From: jw schultz <jw@pegasys.ws>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Fwd: Re: Kernel 2.4 CPU Arch issues]
Date: Mon, 21 Jul 2003 12:23:43 -0700 [thread overview]
Message-ID: <20030721192343.GA5537@pegasys.ws> (raw)
In-Reply-To: <1058769556.6977.2.camel@dhcp22.swansea.linux.org.uk>
On Mon, Jul 21, 2003 at 07:39:16AM +0100, Alan Cox wrote:
> On Llu, 2003-07-21 at 01:25, William M. Quarles wrote:
> > Well, wouldn't changing the gcc -march option and/or adding -mcpu
> > options for the various processors in the Makefile make a difference, as
> > the patchfile suggests?
>
> Currently - no. gcc knows a lot more processor names that require individual
> unique optimisation
no && s/that/than/
--
________________________________________________________________
J.W. Schultz Pegasystems Technologies
email address: jw@pegasys.ws
Remember Cernan and Schmitt
next prev parent reply other threads:[~2003-07-21 19:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-20 23:29 [Fwd: Re: Kernel 2.4 CPU Arch issues] William M. Quarles
2003-07-21 0:00 ` Alan Cox
2003-07-21 0:25 ` William M. Quarles
2003-07-21 6:39 ` Alan Cox
2003-07-21 19:23 ` jw schultz [this message]
2003-07-23 1:17 ` J.A. Magallon
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=20030721192343.GA5537@pegasys.ws \
--to=jw@pegasys.ws \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).