h8300, m32c and PRIuPTR

Yaakov Selkowitz yselkowi@redhat.com
Mon Mar 16 19:59:00 GMT 2015

On Mon, 2015-03-16 at 14:32 -0500, Joel Sherrill wrote:
> On 3/16/2015 2:25 PM, Yaakov Selkowitz wrote:
> > On Mon, 2015-03-16 at 13:02 -0500, Joel Sherrill wrote:
> >> But remember, not every newlib target is an RTEMS target.  This balance
> >> could shift based on the other bare machine targets.  Does someone
> >> have *-elf targets handy for targets that do not have RTEMS to test using
> >> my script and test case?
> > Attached are what I ended up with after fixing the warnings.
> >
> Thanks!!! Can you add a unique #warning to each #define case and
> see what the distribution is?
> I hacked on my version and ended up with this:
>       2     #warning "CASE: 1 long long only"
>       8      #warning "CASE: 2 long but use int"
>       7      #warning "CASE: 3 long use long"
>       4      #warning "CASE: 4 int use int"

11 CASE: 1
147 CASE: 2
88 CASE: 3
11 CASE: 4

> I could fold the two cases in the "long long" block into one. Maybe
> you have a target that uses the second case.

None of my targets used __STRINGIFY(ll##x).

> That will let us know how the if/else should go.  Of course, one
> school of thought is that **ALL** targets should be listed and
> you get an error otherwise. That ensures that no one misses
> a spot where a porter should look.

Note that I'm still missing (at least) the following newlib targets:

avr-elf: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64401
cr16-elf: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64424
iq2000-elf: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64400
m32c-elf: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64403
mep-elf: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64402
or1k-elf: requires GCC 5.0
xstormy16-elf: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64407

I see you mentioned m32c earlier, do you have a patch for gcc-4.9.2?

Yaakov Selkowitz
Associate Software Engineer, ARM
Red Hat, Inc.

More information about the Newlib mailing list