This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/68456] UINT32_TYPE has different type for i586-elf and for i586-unknown-linux
- From: "vaalfreja at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 24 Nov 2015 08:57:43 +0000
- Subject: [Bug target/68456] UINT32_TYPE has different type for i586-elf and for i586-unknown-linux
- Auto-submitted: auto-generated
- References: <bug-68456-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68456
Yulia Koval <vaalfreja at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|INVALID |---
Summary|UINT32_TYPE is long |UINT32_TYPE has different
|unsigned for 32bit targets |type for i586-elf and for
| |i586-unknown-linux
--- Comment #6 from Yulia Koval <vaalfreja at gmail dot com> ---
> The types used in GCC are intended to be consistent with what the libc's
> own headers do (lots of problems will arise if they aren't). Newlib's
> headers, as of when this support was added to GCC, used long in that case,
> a use introduced by <https://sourceware.org/ml/newlib/2005/msg00824.html>,
> apparently because it was convenient for the newlib implementation at that
> time.
And why newlib-stdint header is used in this case? I haven't used any
newlib-related options in configure. These targets still have different types
for UINT32_TYPE.