From: Allan Sandfeld <linux@sneulv.dk>
To: linux-kernel@vger.kernel.org
Subject: Re: On K7, -march=k6 is good (Was Re: Why no -march=athlon?)
Date: Wed, 19 Dec 2001 20:38:41 +0100 [thread overview]
Message-ID: <E16GmY5-0000F5-00@Princess> (raw)
In-Reply-To: <x88r8ptki37.fsf@rpppc1.hns.com> <20011219175616.GD19236@0xd6.org> <x88itb3njfr.fsf@rpppc1.hns.com>
In-Reply-To: <x88itb3njfr.fsf@rpppc1.hns.com>
On Wednesday 19 December 2001 19:39, nbecker@fred.net wrote:
> >>>>> "M" == M R Brown <mrbrown@0xd6.org> writes:
>
> M> Curious, what happens when you compile using gcc 3.0.1 against
> M> -march=athlon?
>
> Is it safe to use gcc-3.0.2 to compile the kernel?
>
If it compiles.. Otherwise use gcc-3.0.3(prerelease), it has fixes that makes
the _current_ kernel compile.
<sarcasm>
Obviously it's still full of bugs, it wouldn't really be gcc if it wasn't.
</sarcasm>
I am currently running a linux-2.4.16-gcc3, where the only changed part is
the use of the gcc-3.0 compiler, and a -foptimize-siblings-calls flag. It's
running smoothly, although I havn't done any performance test yet.
Btw. I havent found anything that compiles with gcc-3.1 yet.
next prev parent reply other threads:[~2001-12-19 19:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-17 14:59 Why no -march=athlon? nbecker
2001-12-17 15:54 ` Dominik Mierzejewski
2001-12-17 17:40 ` M. R. Brown
2001-12-19 17:46 ` On K7, -march=k6 is good (Was Re: Why no -march=athlon?) Benoit Poulot-Cazajous
2001-12-19 17:56 ` M. R. Brown
2001-12-19 18:39 ` nbecker
2001-12-19 18:47 ` M. R. Brown
2001-12-19 18:52 ` J Sloan
2001-12-19 19:01 ` Josh McKinney
2001-12-19 19:21 ` M. R. Brown
2001-12-19 19:28 ` J Sloan
2001-12-19 19:38 ` Allan Sandfeld [this message]
2001-12-19 21:40 ` Benoit Poulot-Cazajous
-- strict thread matches above, loose matches on Subject: below --
2001-12-19 20:33 RaúlNúñez de Arenas Coronado
2001-12-20 0:06 ` Alessandro Suardi
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=E16GmY5-0000F5-00@Princess \
--to=linux@sneulv.dk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.