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: "'gcc at gnu dot org'" <gcc at gnu dot org>
- Date: Wed, 30 Jul 2003 10:24:00 -0700
- Subject: Re: incorrect __vxworks__ usage in longlong.h (3.3) was ok in 3.2.3
- References: <FE045D4D9F7AED4CBFF1B3B813C8533702857267@mail.sandvine.com>
Ken Faiczak <kfaiczak@sandvine.com> writes:
> Not sure how this creeped in but it breaks all vxworks builds
> for anything else other than PPC (in my case MIPS)
>
> it really needs to be removed.
> better to force the vxworks build to define __powerpc__ or something like
> that
> than to break the compiler for all vxworks builds that define stuff
> before this point in the file..
GCC 3.3 defines _ARCH_PPC for a vxworks/ppc compiler, so you should be
able to just remove the reference to __vxworks__ from the second
#ifdef. A patch to that effect is pre-approved.
The bug was introduced by this change:
revision 1.30
date: 2002/08/27 14:55:41; author: dje; state: Exp; lines: +88 -80
branches: 1.30.2; 1.30.4;
* longlong.h: Import current PowerPC defintion from GMP-4.1.
* config/rs6000/rs6000.h (MIN_UNITS_PER_WORD): Add IN_LIBGCC2 case.
* config/rs6000/linux64.h (ADJUST_FIELD_ALIGN): Undef before define.
so I would encourage you to raise this issue with the GMP maintainers
as well; they probably have the bug in their version of this file.
zw