From: Andreas Jaeger <aj@suse.de>
To: Joseph Carter <knghtbrd@debian.org>
Cc: Ville Herva <vherva@mail.niksula.cs.hut.fi>,
"Mike A. Harris" <mharris@opensourceadvocate.org>,
Linux Kernel mailing list <linux-kernel@vger.kernel.org>,
jh@suse.cz
Subject: Re: [Semi-OT] Dual Athlon support in kernel
Date: 24 Apr 2001 13:11:01 +0200 [thread overview]
Message-ID: <ho4rve364a.fsf@gee.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0104240115050.21785-100000@asdf.capslock.lan> <3AE52C2C.C6B2B472@mountain.net> <20010424131857.F3529@niksula.cs.hut.fi> <20010424033922.A5878@debian.org>
In-Reply-To: <20010424033922.A5878@debian.org> (Joseph Carter's message of "Tue, 24 Apr 2001 03:39:22 -0700")
Joseph Carter <knghtbrd@debian.org> writes:
> On Tue, Apr 24, 2001 at 01:18:57PM +0300, Ville Herva wrote:
> > There's also AthlonLinux http://athlonlinux.org/ and AthlonGCC
> > http://athlonlinux.org/agcc/about.shtml, but I have no experience with those
> > (I have no Athlon ;( ).
>
> A warning about agcc, I've discovered that it does not always compile code
> quite the way you expect it. This is unsurprising given it's based on
> pgcc which is known to change alignments on you in ways that sometimes
> break things subtly.
>
>
> I do not know if agcc actually can produce code which simply does not work
> as is reported with pgcc (I suspect the alignment differences account for
> many of those cases), but I recall reading in the past few days that agcc
> is not supported for compiling the kernel.
>
> It also fails to properly compile certain other programs, notably anything
> that includes asm functions. As a result, my own experience suggests you
> consider agcc in the same class as gcc 3.0 at the moment - experimental.
> Hopefully the k7 optimizations that work well will find their way into a
> nice athlon subarch options in standard gcc and agcc won't be necessary.
Note that gcc 3.0 will have support for Athlons, -mcpu=athlon and
-march=athlon are both supported and will do the right thing. For
details you should ask Jan Hubicka who implemented this some time ago,
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
next prev parent reply other threads:[~2001-04-24 11:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-24 5:22 [Semi-OT] Dual Athlon support in kernel Mike A. Harris
2001-04-24 6:05 ` Andrea Arcangeli
2001-04-24 7:33 ` Tom Leete
2001-04-24 10:18 ` Ville Herva
2001-04-24 10:39 ` Joseph Carter
2001-04-24 10:55 ` [Fully-OT] " Ville Herva
2001-04-24 11:11 ` Andreas Jaeger [this message]
2001-04-24 23:18 ` [Semi-OT] " Martin Clausen
2001-04-26 23:01 ` Jakob Østergaard
-- strict thread matches above, loose matches on Subject: below --
2001-04-24 6:03 Antwerpen, Oliver
2001-04-24 6:15 ` Andrea Arcangeli
2001-04-24 6:30 ` Miles Lane
2001-04-24 6:22 Antwerpen, Oliver
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=ho4rve364a.fsf@gee.suse.de \
--to=aj@suse.de \
--cc=jh@suse.cz \
--cc=knghtbrd@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mharris@opensourceadvocate.org \
--cc=vherva@mail.niksula.cs.hut.fi \
/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