From: Richard Henderson <rth@twiddle.net>
To: Dave Jones <davej@codemonkey.org.uk>,
Jeff Garzik <jgarzik@pobox.com>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
arjanv@redhat.com, Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: [BK/PATCH] better i386 compiler flags
Date: Sat, 11 Jan 2003 23:29:39 -0800 [thread overview]
Message-ID: <20030111232939.A25494@twiddle.net> (raw)
In-Reply-To: <20030112000601.GE25493@codemonkey.org.uk>; from davej@codemonkey.org.uk on Sun, Jan 12, 2003 at 12:06:02AM +0000
On Sun, Jan 12, 2003 at 12:06:02AM +0000, Dave Jones wrote:
> As a heads up, judging from gcc-patches, it seems that the gcc folks are
> changing -march over to -mtune at some point soon. I can't fathom the
> reasoning behind this other than causing a PITA for users.
No, -mcpu -> -mtune. Reason: mcpu means different things
to different targets, and it's confusing.
r~
next prev parent reply other threads:[~2003-01-12 7:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-11 1:26 [BK/PATCH] better i386 compiler flags Jeff Garzik
2003-01-12 0:06 ` Dave Jones
2003-01-12 7:29 ` Richard Henderson [this message]
2003-01-12 14:52 ` Dave Jones
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=20030111232939.A25494@twiddle.net \
--to=rth@twiddle.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjanv@redhat.com \
--cc=davej@codemonkey.org.uk \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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