From: Eric Christopher <echristo@redhat.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Chris Demetriou <cgd@broadcom.com>,
"Maciej W. Rozycki" <macro@ds2.pg.gda.pl>,
linux-mips@linux-mips.org
Subject: Re: gcc support for mips32 release 2]
Date: Thu, 18 Mar 2004 15:03:34 -0800 [thread overview]
Message-ID: <1079651013.3383.0.camel@dzur.sfbay.redhat.com> (raw)
In-Reply-To: <20040318225154.GA761@linux-mips.org>
> It seems a small problem compared to having to answer all the questions
> about why Linux tries to optimize for processor X when it's configured
> for type Y. People just love tweaking compiler flags it seems - even if
> not necessarily knowing all the consequences ...
Amen brother.
-eric
--
Eric Christopher <echristo@redhat.com>
next prev parent reply other threads:[~2004-03-18 23:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-05 22:29 gcc support for mips32 release 2] Eric Christopher
2004-03-17 16:18 ` Maciej W. Rozycki
2004-03-17 16:41 ` cgd
2004-03-17 18:44 ` Maciej W. Rozycki
2004-03-18 22:51 ` Ralf Baechle
2004-03-18 23:03 ` Eric Christopher [this message]
2004-03-19 14:16 ` Maciej W. Rozycki
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=1079651013.3383.0.camel@dzur.sfbay.redhat.com \
--to=echristo@redhat.com \
--cc=cgd@broadcom.com \
--cc=linux-mips@linux-mips.org \
--cc=macro@ds2.pg.gda.pl \
--cc=ralf@linux-mips.org \
/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