From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28074 invoked by alias); 26 Feb 2003 22:12:44 -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 28048 invoked by uid 48); 26 Feb 2003 22:12:44 -0000 Date: Wed, 26 Feb 2003 22:12:00 -0000 Message-ID: <20030226221244.28047.qmail@sources.redhat.com> To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, jbr@keyresearch.com, jbroughton@keyresearch.com, glindahl@keyresearch.com, nobody@gcc.gnu.org, rsandifo@sources.redhat.com From: rsandifo@sources.redhat.com Reply-To: rsandifo@sources.redhat.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, jbr@keyresearch.com, jbroughton@keyresearch.com, glindahl@keyresearch.com, nobody@gcc.gnu.org, rsandifo@sources.redhat.com, gcc-gnats@gcc.gnu.org Subject: Re: target/8520: [mips-linux] -mips64 not forcing -mgp64 under mips*-*-linux* target X-SW-Source: 2003-02/txt/msg01401.txt.bz2 List-Id: Synopsis: [mips-linux] -mips64 not forcing -mgp64 under mips*-*-linux* target Responsible-Changed-From-To: unassigned->rsandifo Responsible-Changed-By: rsandifo Responsible-Changed-When: Wed Feb 26 22:12:44 2003 Responsible-Changed-Why: mine State-Changed-From-To: open->feedback State-Changed-By: rsandifo State-Changed-When: Wed Feb 26 22:12:44 2003 State-Changed-Why: Has there been any response to Daniel's message? FWIW, I agree with what he said. The mips options were discussed on the gcc lists a while ago. In the end, it was agreed that the architecture flags should not change the ABI (and therefore should not change the register size). It's useful to have "mips-linux-gnu -mips4" generate 32-bit MIPS IV code, for example. Very few configurations can handle a change in register size gracefully. Note that 3.4 will support a mips64-linux-gnu configuration. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8520