From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10488 invoked by alias); 26 Oct 2004 18:52:27 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 10477 invoked by uid 48); 26 Oct 2004 18:52:26 -0000 Date: Tue, 26 Oct 2004 18:52:00 -0000 Message-ID: <20041026185226.10476.qmail@sourceware.org> From: "rsandifo at gcc dot gnu dot org" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20040730103701.16830.magnus.bergman@observer.net> References: <20040730103701.16830.magnus.bergman@observer.net> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug target/16830] Including with -mabi=n32 causes an error. X-Bugzilla-Reason: CC X-SW-Source: 2004-10/txt/msg03215.txt.bz2 List-Id: ------- Additional Comments From rsandifo at gcc dot gnu dot org 2004-10-26 18:52 ------- Confirmed. Of the two choices you mention, I think it would be better to remove the R3000 and R4000 macros for IRIX. Another option would be to use fixincludes, but I think removing the macros is better. Like you say, MIPSpro doesn't define them, even in underscore form, and they've always been a bit flawed anyway. [ Reasoning: the macros sound like they're indicators of the target ISA, but they really indicators of "64-bitness". __mips is a better choice if you want to know the specific ISA level and __mips64 is better if you just want to know whether the code is 64-bit or not. ] I'll try to bootstrap the obvious patch soon, but the irix box I use is a bit under the weather right now. -- What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|unassigned at gcc dot gnu |rsandifo at gcc dot gnu dot |dot org |org Status|UNCONFIRMED |ASSIGNED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16830