This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: use of bfd_stdint.h from src/include
- From: "Joseph S. Myers" <joseph at codesourcery dot com>
- To: Doug Evans <dje at sebabeach dot org>
- Cc: binutils at sourceware dot org
- Date: Tue, 6 Oct 2009 17:06:33 +0000 (UTC)
- Subject: Re: use of bfd_stdint.h from src/include
- References: <20091006165616.4BF476E3D9@sebabeach.org>
On Tue, 6 Oct 2009, Doug Evans wrote:
> Hi.
>
> Is it ok for files in src/include to use bfd_stdint.h?
> [I realize include/opcode/ppc.h uses it,
> I'm just looking for confirmation that it's generally ok.
> Unnecessary dependencies on bfd seems, umm, yucky. :-)]
>
> include/plugin-api.h uses stdint.h directly,
The subset of files in include that is shared with GCC (including
plugin-api.h) has to be closed under inclusion, so it can't use
bfd_stdint.h as that isn't shared with GCC.
> but perhaps it has less portability concerns.
Its use of stdint.h is a bug.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40790
> Or is it now ok to use stdint.h from src/include in general?
Each tool may have its own portability requirements, but in general for
GCC and src they are for a C90 compiler and maybe some C90 library defects
can get fixed up by libiberty rather than requiring a C90 library; they
certainly aren't for a C99 compiler or library.
--
Joseph S. Myers
joseph@codesourcery.com