public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Sandiford <rsandifo@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gcc-patches@sources.redhat.com, echristo@redhat.com
Subject: Re: RFC: New approach to --with-cpu
Date: Wed, 31 Jul 2002 06:54:00 -0000	[thread overview]
Message-ID: <wvn1y9kf2au.fsf@talisman.cambridge.redhat.com> (raw)
In-Reply-To: <20020731132428.GA28270@nevyn.them.org>

Daniel Jacobowitz <drow@mvista.com> 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 ;-)

Richard

  reply	other threads:[~2002-07-31 13:35 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-30 15:27 Daniel Jacobowitz
2002-07-31  6:35 ` Richard Sandiford
2002-07-31  6:41   ` Daniel Jacobowitz
2002-07-31  6:54     ` Richard Sandiford [this message]
2002-07-31  7:28       ` Daniel Jacobowitz
2002-07-31  7:36         ` Richard Sandiford
2002-07-31  7:46           ` Daniel Jacobowitz
2002-07-31  7:50             ` Richard Sandiford
2002-07-31  8:04               ` Daniel Jacobowitz
2002-07-30 18:54 John David Anglin
2002-07-30 23:03 ` Daniel Jacobowitz
2002-07-31  7:53   ` John David Anglin
2002-07-31  8:09     ` Daniel Jacobowitz
2002-07-31  8:30       ` Richard Earnshaw
2002-07-31  9:02         ` Daniel Jacobowitz
2002-07-31 10:34           ` John David Anglin
2002-07-31 13:27             ` Daniel Jacobowitz
2002-08-01  3:31               ` Richard Sandiford
2002-08-01  3:57                 ` Richard Earnshaw
2002-08-01  8:15               ` John David Anglin
2002-08-01  8:23                 ` Daniel Jacobowitz
2002-08-01 11:40                   ` John David Anglin
2002-08-01  6:30             ` Richard Earnshaw
2002-08-01  7:41               ` John David Anglin
     [not found] <20020801125224.GA5374@nevyn.them.org>
2002-08-01  6:04 ` Richard Earnshaw
2002-08-01  6:25   ` Daniel Jacobowitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=wvn1y9kf2au.fsf@talisman.cambridge.redhat.com \
    --to=rsandifo@redhat.com \
    --cc=drow@mvista.com \
    --cc=echristo@redhat.com \
    --cc=gcc-patches@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).