From: "H . J . Lu" <hjl@lucon.org>
To: Eric Christopher <echristo@redhat.com>
Cc: Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>,
binutils@sources.redhat.com
Subject: Re: [PATCH] Disable warning about -mcpu
Date: Thu, 06 Sep 2001 22:35:00 -0000 [thread overview]
Message-ID: <20010906223542.A1866@lucon.org> (raw)
In-Reply-To: <999837123.1533.37.camel@ghostwheel.cygnus.com>
On Thu, Sep 06, 2001 at 09:32:02PM -0700, Eric Christopher wrote:
> 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.
>
> >
> > + /* We should warn about deprecated -mcpu, but gcc 3.0 needs it.
> > + Commented out for now. */
FWIW, I'd like to see all those mips backend fixes go into gcc 3.0.x.
As far as I am concerned, gcc 3.0.x is broken on Linux/mips. I only
track the main trunk for Linux/mips.
H.J.
prev parent reply other threads:[~2001-09-06 22:35 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
2001-09-06 22:35 ` H . J . Lu [this message]
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=20010906223542.A1866@lucon.org \
--to=hjl@lucon.org \
--cc=binutils@sources.redhat.com \
--cc=echristo@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).