From: "J.A. Magallon" <jamagallon@able.es>
To: Ruth Ivimey-Cook <Ruth.Ivimey-Cook@ivimey.org>
Cc: Luigi Genoni <kernel@Expansa.sns.it>, Dave Jones <davej@suse.de>,
"J.A. Magallon" <jamagallon@able.es>,
Luca Barbieri <ldb@ldb.ods.org>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
Linux-Kernel ML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] [2.4] [2.5] [i386] Add support for GCC 3.1 -march=pentium{-mmx,3,4}
Date: Sun, 26 May 2002 03:08:49 +0200 [thread overview]
Message-ID: <20020526010849.GA10643@werewolf.able.es> (raw)
In-Reply-To: <Pine.LNX.4.44.0205260044270.10923-100000@sharra.ivimey.org>
On 2002.05.26 Ruth Ivimey-Cook wrote:
>On Sun, 26 May 2002, Luigi Genoni wrote:
>>On Sun, 26 May 2002, Dave Jones wrote:
>>> On Sun, May 26, 2002 at 01:37:39AM +0200, J.A. Magallon wrote:
>>> > Could you also split
>>> > Pentium-Pro/Celeron/Pentium-II CONFIG_M686
>>> > into
>>> > Pentium-Pro CONFIG_M686
>>> > Pentium-II/Celeron CONFIG_MPENTIUMII
>>> There are also a few extra Athlon targets iirc. athlon-xp and the like,
>>> which I'm not sure the purpose of. Some gcc know-all want to clue me in
>>> to what these offer over -march=athlon ?
>>>
>>I do not know about the gcc options, but Athlon XP/MP has sse instruction,
>>while tbird has not, so it could be relate to this.
>>
Problem is that CPU selection is not based on cpu itself, but in options
offered by previous gcc compilers.
I think that the menu should contain separate config options for each
processor type, so it is easily modifiable for specific optimizations
offered by new compilers (for example, gcc-3.1 splitting i686 in
pentium-pro, p2, p3 and p4), or some braindead hacker can optimize
code snippets for some kind of processor.
--
J.A. Magallon # Let the source be with you...
mailto:jamagallon@able.es
Mandrake Linux release 8.3 (Cooker) for i586
Linux werewolf 2.4.18 #1 SMP sáb may 25 14:44:46 CEST 2002 i686
next prev parent reply other threads:[~2002-05-26 0:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-25 21:01 [PATCH] [2.4] [2.5] [i386] Add support for GCC 3.1 -march=pentium{-mmx,3,4} Luca Barbieri
2002-05-25 23:37 ` J.A. Magallon
2002-05-25 22:53 ` Dave Jones
2002-05-25 23:29 ` Luigi Genoni
2002-05-25 23:49 ` Ruth Ivimey-Cook
2002-05-26 0:30 ` Dave Jones
2002-05-27 8:53 ` Pavel Machek
2002-05-29 11:42 ` Dave Jones
2002-05-29 19:57 ` Pavel Machek
2002-05-30 6:40 ` Jan Hubicka
2002-05-30 10:25 ` David Woodhouse
2002-05-30 10:45 ` Jan Hubicka
2002-05-26 1:08 ` J.A. Magallon [this message]
2002-05-26 0:21 ` Dave Jones
[not found] ` <1022380785.11859.59.camel@irongate.swansea.linux.org.uk>
2002-05-26 9:11 ` J.A. Magallon
2002-05-26 19:14 ` Alan Cox
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=20020526010849.GA10643@werewolf.able.es \
--to=jamagallon@able.es \
--cc=Ruth.Ivimey-Cook@ivimey.org \
--cc=davej@suse.de \
--cc=kernel@Expansa.sns.it \
--cc=ldb@ldb.ods.org \
--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 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.