This is the mail archive of the
newlib@sourceware.org
mailing list for the newlib project.
Re: stdbool.h ?
- From: "Emmanuel Blot" <eblot dot ml at gmail dot com>
- To: "Jon Beniston" <jon at beniston dot com>
- Cc: newlib at sourceware dot org
- Date: Thu, 26 Sep 2019 14:08:11 +0200
- Subject: Re: stdbool.h ?
- References: <D884142B-CEC1-425C-BF8E-CD1DF7B50129@gmail.com> <051a01d5745c$68732ed0$39598c70$@beniston.com>
Hi Jon,
On 26 Sep 2019, at 13:20, Jon Beniston wrote:
That's usually provided by gcc.
I’m using LLVM :)
I just discovered that the host’s stdbool.h was used up to now - which
is fortunately target agnostic.
./lib/gcc/target/version/include/stdbool.h
GCC also provides its own stdint.h (including either an external
stdint.h or its own), so I’m surprised the behaviour is different with
stdbool.h.
As I understand it - maybe I’m wrong - stdbool.h is part of the C
Standard Library, so should not it be part of the newlib C
implementation as well? I know the boundary between the compiler and the
C library is somewhat tricky, but it is kind of weird stdint.h and
stdbool.h are somewhat handled differently.
Thanks,
Emmanuel.