From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28980 invoked by alias); 31 Jul 2002 13:41:31 -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 28970 invoked from network); 31 Jul 2002 13:41:29 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by sources.redhat.com with SMTP; 31 Jul 2002 13:41:29 -0000 Received: from dsl254-114-118.nyc1.dsl.speakeasy.net ([216.254.114.118] helo=nevyn.them.org ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 17ZtjG-0007ju-00; Wed, 31 Jul 2002 08:41:30 -0500 Received: from drow by nevyn.them.org with local (Exim 3.35 #1 (Debian)) id 17ZtjG-0007bl-00; Wed, 31 Jul 2002 09:41:30 -0400 Date: Wed, 31 Jul 2002 07:28:00 -0000 From: Daniel Jacobowitz To: Richard Sandiford Cc: gcc-patches@sources.redhat.com, echristo@redhat.com Subject: Re: RFC: New approach to --with-cpu Message-ID: <20020731134130.GA29129@nevyn.them.org> Mail-Followup-To: Richard Sandiford , gcc-patches@sources.redhat.com, echristo@redhat.com References: <20020730215824.GA21681@nevyn.them.org> <20020731132428.GA28270@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.1i X-SW-Source: 2002-07/txt/msg01865.txt.bz2 On Wed, Jul 31, 2002 at 02:35:21PM +0100, Richard Sandiford wrote: > Daniel Jacobowitz writes: > > > I suppose you could have: > > > > > > if (!option_present (*argcp, *argvp, "-march=") > > > && (!option_present (*argcp, *argvp, "-mips") > > > || option_present (*argcp, *argvp, "-mips16"))) > > > add_option (argcp, argvp, "-march=" XSTRING (TARGET_DEFAULT_OPTION_ARCH)); > > > > > > (since -mips16 shouldn't change the default arch) but maybe > > > there needs to be some sort of target macro? > > > > That doesn't do quite the right thing, if you think about the logic. > > It'd have to be "-mips1" or "-mips2" or "-mips3" or "-mips4" or > > "-mips5" (?) or "-mips32" or "-mips64". > > Well, all -mips* options are handled by one entry in TARGET_SWITCHES, so > -mips16 overrides a previous -mips3, silly as that might be. I guess to > be fully correct, you need to see if the last -mips option is -mips16, in > which case you keep the default, or something else, in which case you > don't. (half ;-) Wait, wait a second here. I forgot to re-ask the basic question: if the user configures --with-cpu=, and then runs the compiler with -mips3, what _should_ happen and what _will_ happen? The result will be both -march= and -mips3 being specified on the command line; will the -mips3 be ignored or have some effect? You're much more familiar with this code than I am... -- Daniel Jacobowitz Carnegie Mellon University MontaVista Software Debian GNU/Linux Developer