From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8012 invoked by alias); 31 Jul 2002 14:45:58 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 7937 invoked from network); 31 Jul 2002 14:45:54 -0000 Received: from unknown (HELO executor.cambridge.redhat.com) (195.224.55.237) by sources.redhat.com with SMTP; 31 Jul 2002 14:45:54 -0000 Received: from talisman.cambridge.redhat.com (talisman.cambridge.redhat.com [172.16.18.81]) by executor.cambridge.redhat.com (Postfix) with ESMTP id 60F1AABAF8; Wed, 31 Jul 2002 15:45:53 +0100 (BST) Received: (from rsandifo@localhost) by talisman.cambridge.redhat.com (8.11.6/8.11.0) id g6VEjr610659; Wed, 31 Jul 2002 15:45:53 +0100 X-Authentication-Warning: talisman.cambridge.redhat.com: rsandifo set sender to rsandifo@redhat.com using -f To: Daniel Jacobowitz Cc: gcc-patches@sources.redhat.com, echristo@redhat.com Subject: Re: RFC: New approach to --with-cpu References: <20020730215824.GA21681@nevyn.them.org> <20020731132428.GA28270@nevyn.them.org> <20020731134130.GA29129@nevyn.them.org> <20020731143643.GA30227@nevyn.them.org> From: Richard Sandiford Date: Wed, 31 Jul 2002 07:50:00 -0000 In-Reply-To: <20020731143643.GA30227@nevyn.them.org> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2002-07/txt/msg01869.txt.bz2 Daniel Jacobowitz writes: > Well, the best I can do given the -mipsN situation... how does this > revision look to you? The new macro looks good. I still think there should be some -mips16 exemption, though. Specifying -mips16 and some other -mipsN option isn't supported, so if -mips16 does occur on the command line, I think we should assume the user wants the default architecture. Richard