diff options
author | Joel Brobecker <brobecker@adacore.com> | 2015-03-02 06:01:23 -0800 |
---|---|---|
committer | Joel Brobecker <brobecker@adacore.com> | 2015-03-02 06:02:11 -0800 |
commit | cc7039d31aefe14a31b5b6d8d3694e32bc22b486 (patch) | |
tree | cb0258c80080a147c8a5a825832b86bd3ed8d73c /gdb/utils.c | |
parent | 4fa5d7b436815f58688ec9245f24fc83263364b9 (diff) | |
download | gdb-cc7039d31aefe14a31b5b6d8d3694e32bc22b486.zip gdb-cc7039d31aefe14a31b5b6d8d3694e32bc22b486.tar.gz gdb-cc7039d31aefe14a31b5b6d8d3694e32bc22b486.tar.bz2 |
Remove use of stdbool.h in GDB sources.
Using type bool from stdbool unfortunately causes problems trying
to build GDB on AiX and Solaris:
In file included from ../../src/gdb/utils.h:24:0,
from ../../src/gdb/defs.h:707,
from ../../src/gdb/utils.c:20:
/[...]/curses.h:96:14: error: two or more data types in declaration
specifiers
typedef char bool;
^
make[2]: *** [utils.o] Error 1
In theory, the problem is in curses.h which, in both cases, do
something similar. On Solaris:
#if !defined(__cplusplus) && !defined(_BOOL)
typedef char bool;
#endif /* !defined(__cplusplus) && !defined(_BOOL) */
On AiX:
#if !defined(__cplusplus) || (defined(__IBMCPP__) &&(__IBMCPP__<400))
#ifndef _BOOL
#define _BOOL
typedef int bool;
#endif
#endif
You can reproduce the same problem by trying to compile:
% cat toto.c
#include <stdbool.h>
#include <curses.h>
% gcc -c toto.c
In file included from toto.c:1:0:
/[...]/curses.h:159:13: error: two or more data types in declaration
specifiers
typedef int bool;
^
This specific issue wouldn't occur if we included curses.h before
including stdbool.h, and I looked at that just to be complete.
Here is a small schematic representation of the include logic:
* utils.c:
-> defs.h -> utils.h -> stdbool.h
-> gdb_curses.h -> curses.h
Because defs.h should always be first on the list, it means that
stdbool.h will always necessarily be included ahead of curses.h.
But, thinking beyond this very specific issue, it shows that using
stdbool.h is going to cause problems on these systems until either
GCC fixes those includes in a way that makes them work; or we switch
to C++.
In the meantime, I think the path of least resistance is to revert
the use of stdbool.h, and use integers, the way we've done up until
now. The benefits of using type "bool" are modest, IMO, so not
a great loss, and a temporary one.
gdb/ChangeLog:
* utils.h: Remove <stdbool.h> #include.
(producer_is_gcc): Change return type to "int".
* utils.c (producer_is_gcc): Change return type to int.
Return 1 instead of true, and 0 instead of false.
Adjust function documentation accordingly.
Diffstat (limited to 'gdb/utils.c')
-rw-r--r-- | gdb/utils.c | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/gdb/utils.c b/gdb/utils.c index 3ce5814..4f9f4f0 100644 --- a/gdb/utils.c +++ b/gdb/utils.c @@ -3269,11 +3269,11 @@ producer_is_gcc_ge_4 (const char *producer) return minor; } -/* Returns true if the given PRODUCER string is GCC and sets the MAJOR - and MINOR versions when not NULL. Returns false if the given PRODUCER +/* Returns nonzero if the given PRODUCER string is GCC and sets the MAJOR + and MINOR versions when not NULL. Returns zero if the given PRODUCER is NULL or it isn't GCC. */ -bool +int producer_is_gcc (const char *producer, int *major, int *minor) { const char *cs; @@ -3299,11 +3299,11 @@ producer_is_gcc (const char *producer, int *major, int *minor) if (*cs && isspace (*cs)) cs++; if (sscanf (cs, "%d.%d", major, minor) == 2) - return true; + return 1; } /* Not recognized as GCC. */ - return false; + return 0; } /* Helper for make_cleanup_free_char_ptr_vec. */ |