public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@suse.de>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: 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 00:53:59 +0200	[thread overview]
Message-ID: <20020526005359.E16102@suse.de> (raw)
In-Reply-To: <1022360474.21238.5.camel@ldb> <20020525233739.GA2022@werewolf.able.es>

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
 > 
 > Gcc-3.1 has also a -march=pentium2 specific target, that is not a synomym
 > for any other.

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 ?

 > BTW, I think an option to enable -mmmx would also be useful. Nothing more,
 > because afaik sse is only floating point.

Another interesting recently-added option which may be worth
benchmarking on modern CPUs is the prefetch-loops option.
In a lot of cases, the kernel 'knows better' and is adding the
prefetches itself, but it may be interesting to see what difference
gcc can make here. (More interesting would be examining the output to
see *where* gcc is putting the prefetches)

Given the immaturity of all these options, I'd doubt they're that good
an idea for 2.4. Getting them tested during 2.5 may prove to get any
bugs shaken out in time for $compiler_of_the_choice for 2.6 though.

    Dave

-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs

  reply	other threads:[~2002-05-25 22:54 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 [this message]
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
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=20020526005359.E16102@suse.de \
    --to=davej@suse.de \
    --cc=jamagallon@able.es \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox