| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In compiler.h, it adds the missing "std::" namespace prefixes to the
memory_barrier() definition.
In gpsd.h it:
1) Moves the include of compiler.h outside the conditional 'extern
"C"', since the "atomic" stuff in the former is incompatible with the
latter.
2) Fixes DEVICEHOOKPATH for C++11 (C++11 requires spaces between
literals and string macros).
3) Cleans up some ordering of system includes left over from the
former head/tail setup.
TESTED:
Ran "scons build-all check" on OSX 10.5-10.12, Ubuntu 14, CentOS 7,
Fedora 25, FreeBSD 10.3, OpenBSD 5.6 (32- and 64-bit), and NetBSD
6.1.5. Also tested Qt builds with OSX 10.9 (Qt4 and Qt5), OSX 10.12
(Qt5), and Fedora 25 (Qt5).
Observed the correct DEVICEHOOKPATH in the log on OSX.
|
|
|
|
|
|
|
|
|
|
| |
For atomics:
C98 and above needs <stdatomic.h>
C++11 and above needs <atomic>
C++98 and C++03 have no atomics
So this leaves a little hole where we have no atomics for C++98 and
C++03. So C++ clients need tp be careful...
|
| |
|
|
|
|
| |
Signed-off-by: Gary E. Miller <gem@rellim.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The proximate cause was that we've been seing emission of error
messages that were randomly and disturbingly variable across different
environments - notably Raspbian and Gentoo splint gave nontrivially
different results than Ubuntu 14.10 splint. And this was *not* due to
Ubuntu patches! A pristine splint built from the 3.1.2 tarball on
Ubuntu didn't match the Raspbian and Gentoo results either.
But this has been coming for a while. Easy access to more modern
static analyzers such as coverity, scan-build and cppcheck has been
decreasing the utility of splint, which is unmaintained and somewhat
buggy and not easy to use.
Only file not cleaned is ppsthread.c, because Gary has been working
on it during this cleanup.
All regression tests pass. PPS observed live on GR601-W.
|
| |
|
|
|
|
|
|
|
|
| |
If a pointer (not array) is passed to NITEMS() macro, gcc will emit
compilation warning.
The actual check is based on newly added COMPILE_CHECK_IS_ARRAY macro.
The change doesn't affect generated binary code.
|
|
|
|
|
|
| |
With -Werror -DNDEBUG, these two cases end up failing with unused variables
(gcc 4.9 with lots of patches on Linux). The attached patch solves the issue
for me, but it's possible that it might be better with the UNUSEDs wrapped in
|
| |
|
|
|
|
| |
It wasn't being used, anyway. There's no Windows port yet.
|
|
|
|
| |
Builds fine, untested.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
All regression tests pass.
|
|
|
|
| |
All regression tests pass with CC=clang.
|
| |
|
|
|
|
| |
All regression tests pass.
|
| |
|
|
Use new macros (UNUSED, PRINTF_FUNC) where appropriate.
This change doesn't affect generated binary code.
|