From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32223 invoked by alias); 5 Aug 2002 22:26:02 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 32208 invoked by uid 71); 5 Aug 2002 22:26:02 -0000 Date: Mon, 05 Aug 2002 15:26:00 -0000 Message-ID: <20020805222602.32207.qmail@sources.redhat.com> To: neil@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: "Dana, Eric" Subject: RE: preprocessor/5806: The preprocessor evaluates expression s in 64-bit, violating IS C++ 16.1.4 Reply-To: "Dana, Eric" X-SW-Source: 2002-08/txt/msg00099.txt.bz2 List-Id: The following reply was made to PR preprocessor/5806; it has been noted by GNATS. From: "Dana, Eric" To: "'Zack Weinberg'" , "Dana, Eric" Cc: "'Neil Booth'" , "'gcc-gnats@gcc.gnu.org'" , "Schoeller, Dick" Subject: RE: preprocessor/5806: The preprocessor evaluates expression s in 64-bit, violating IS C++ 16.1.4 Date: Mon, 5 Aug 2002 17:24:15 -0500 Zack, Although the changes are on the mainline, they aren't implemented for Gcc 3.2.x. The suggestion below does work, but I made the changes to the .h files using a sed script (I wasn't able to get this patch working with fix includes stuff). If the fix includes (on the 3.2.x branch) can be made to make the suggested changes then sequent should be supported. --Eric-- -----Original Message----- From: 'Zack Weinberg' [mailto:zack@codesourcery.com] Sent: Saturday, August 03, 2002 3:53 AM To: Dana, Eric Cc: 'Neil Booth'; 'gcc-gnats@gcc.gnu.org'; Schoeller, Dick Subject: Re: preprocessor/5806: The preprocessor evaluates expression s in 64-bit, violating IS C++ 16.1.4 On Fri, Mar 15, 2002 at 10:37:47AM -0600, Dana, Eric wrote: > Zack, > > The config.guess output is: i386-sequent-sysv4 > One possibility is to change the '#if ((~0UL) == 0xffffffffUL)' to > '#if defined(__i386__)' which is predefined in the gcc compiler. > You may have a better suggestion... Tnx... I believe this has been resolved in the mainline sources; can you check to see whether the problem still persists? Thanks, zw