From: Eric Christopher <echristo@redhat.com>
To: Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>
Cc: binutils@sources.redhat.com
Subject: Re: [PATCH] Disable warning about -mcpu
Date: Thu, 06 Sep 2001 21:32:00 -0000 [thread overview]
Message-ID: <999837123.1533.37.camel@ghostwheel.cygnus.com> (raw)
In-Reply-To: <20010907062637.E351@rembrandt.csv.ica.uni-stuttgart.de>
Ok, I'm not going to approve this one as it is a policy decision for all of
binutils. I'd prefer to leave it in, but I'd rather have Nick give a
comment on whether or not he wants it.
-eric
> this disables warnings about the use of -mcpu=FOO. The idea of it
> was to bring people away from using this to-be-deprecated option,
> but ATM it is an senseless obstacle to anyone who needs to use
> released gcc with a new assembler.
>
>
> Thiemo
>
>
> 2001-09-07 Thiemo Seufer <seufer@csv.ica.uni-stuttgart.de>
> /gas/ChangeLog
> * config/tc-mips.c (md_begin): Disable warning about deprecated
> -mcpu option.
>
>
> diff -BurpNX /bigdisk/src/binutils-exclude src-orig/gas/config/tc-mips.c src/gas/config/tc-mips.c
> --- src-orig/gas/config/tc-mips.c Fri Aug 31 22:00:08 2001
> +++ src/gas/config/tc-mips.c Thu Sep 6 21:58:05 2001
> @@ -995,6 +1044,9 @@ md_begin ()
> "Use -march instead of -mcpu."));
> }
>
> + /* We should warn about deprecated -mcpu, but gcc 3.0 needs it.
> + Commented out for now. */
> +#if 0
> if (mips_arch == CPU_UNKNOWN && mips_cpu != CPU_UNKNOWN)
> {
> ci = mips_cpu_info_from_cpu (mips_cpu);
> @@ -1003,6 +1055,7 @@ md_begin ()
> as_warn (_("The -mcpu option is deprecated. Please use -march and "
> "-mtune instead."));
> }
> +#endif
>
> /* At this point, mips_arch will either be CPU_UNKNOWN if no ARCH was
> specified on the command line, or some other value if one was.
--
Look out behind you!
next prev parent reply other threads:[~2001-09-06 21:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-06 21:26 Thiemo Seufer
2001-09-06 21:32 ` Eric Christopher [this message]
2001-09-06 22:35 ` H . J . Lu
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=999837123.1533.37.camel@ghostwheel.cygnus.com \
--to=echristo@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=ica2_ts@csv.ica.uni-stuttgart.de \
/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).