[Bug 2038] C99 integer type mismatch in GCC and Newlib

[bugzilla-daemon at rtems.org]

https://www.rtems.org/bugzilla/show_bug.cgi?id=2038

--- Comment #15 from Sebastian Huber <sebastian.huber at embedded-brains.de> 2012-04-02 02:26:35 CDT ---
(In reply to comment #14)
> (In reply to comment #13)
> > Created attachment 1464 [details]
> > Alternative stdint.h
> > 
> > Since the only remaining problem in stdint.h after Ralf's first patch was test
> > c99-stdint-1.c.  What about this stdint.h?
> I don't see much sense in this.
> 
> It means to provide a gcc-stdint.h wrapper inside of newlib, even though gcc
> can provide a stdint.h, which is guaranteed to be correct, of its own.

I now don't see much sense in my proposal too ;-)

> >  GCC seems to use int for the
> > pointer integer type when possible.
> No. It's target dependent. Some targets use int, some use long and some (e.g.
> the h8300) alternate between int and long, depending the multilib version being
> in use.

Ok, seems to be quite chaotic on the GCC side.

-- 
Configure bugmail: https://www.rtems.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.