This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: incorrect __vxworks__ usage in longlong.h (3.3) was ok in 3.2.3
- From: "Zack Weinberg" <zack at codesourcery dot com>
- To: Ken Faiczak <kfaiczak at sandvine dot com>
- Cc: 'David Edelsohn' <dje at watson dot ibm dot com>, "'gcc at gnu dot org'" <gcc at gnu dot org>
- Date: Wed, 30 Jul 2003 12:12:26 -0700
- Subject: Re: incorrect __vxworks__ usage in longlong.h (3.3) was ok in 3.2.3
- References: <FE045D4D9F7AED4CBFF1B3B813C853370285726E@mail.sandvine.com>
Ken Faiczak <kfaiczak@sandvine.com> writes:
> Note: also the check of PPC also causes problems for vxworks
> since it also defines that as a CPU_FAMILY for comparison
> even though the current CPU is not equal to that
> (it also defines all kinds of others CPUs and FAMILIES...)
>
> ie in our case CPU=R4000 or CPU=SB1250
>
> is the compiler supposed to be looking for these sorts of things
> that aren't surrounded by __PPC__ sort of thing
It's suboptimal, but please understand that this file is lifted from
GMP, and changes really ought to go through the GMP maintainers.
I don't care to defend vxworks' pollution of the user namespace with
CPU and CPU_FAMILY macros, either.
zw