public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Paul de Vrieze <gentoo-user@devrieze.net>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Automatic cflag downgrade from pentium4 to pentium3?
Date: Thu, 6 Mar 2003 13:34:58 +0100	[thread overview]
Message-ID: <200303061335.06100.gentoo-user@devrieze.net> (raw)
In-Reply-To: <1046953162.27784.8.camel@wolf.codewordt.co.uk>

[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 2313 bytes --]

On Thursday 06 March 2003 13:19, Dhruba Bandopadhyay wrote:
> Hello
>
> Today I saw in a gentoo cvs server email the following.
>
> 2003-03-05 Wednesday 11:01  method
>
>         * sys-devel/gcc/: ChangeLog, gcc-3.2.2-r4.ebuild,
>         files/digest-gcc-3.2.2-r4: replace-flags "-march=pentium4"
>         "-march=pentium3" to fix bug #16867
>
> Now, I realise that the pentium4 is prone to errors but I hope this does
> not begin a spree of changes where -march=pentium4 flags will
> automatically downgraded to -march=pentium3 by the ebuild or otherwise.
>
> I have used pentium4 for some time now with no problems whatsoever and
> would like the raise the issue of whether downgrading of flags should be
> manual and left to the user rather than being automatically modified.  A
> choice would be nice too.
>
> Also, what exactly is responsible for pentium4 bugs?  Is it gcc and is
> there hope of this being resolved with future versions?  And will using
> pentium3 result in a noticeable decline in performance?

The problem with the pentium4 bugs is entirely in gcc. The packages which 
"downgrade" the pentium4 options do that because either:
- the program does not compile with pentium4
- the program does not run with pentium4
- the program is instable with pentium4

In summary the pentium4 flag makes the specific program instable. The loss in 
speed should be minimal provided that -mcpu=pentium4 is still provided. 
Downgrading flags per ebuild I believe is not an option for most users, as it 
makes automatic merging impossible. For this reason the ebuilds that are 
instable with pentium4 edit the cflags so that the generated code is still 
optimized up to the best stable level.

The only other option would be to have all those ebuilds warn the user about 
the problem with march=pentium4, and exit requesting the user to set his/her 
C(XX)FLAGS better. The thing is that most programs actually do work with 
-march=pentium4 so that people might want to use that.

Paul

ps. This flag downgrading concerns only gcc compilation. Not the code 
generated by this gcc. So other programs are still using -march=pentium4 
where it is not filtered too.

-- 
Paul de Vrieze
Researcher
Mail: pauldv@cs.kun.nl
Homepage: http://www.cs.kun.nl/~pauldv

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-03-06 12:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-06 12:19 [gentoo-dev] Automatic cflag downgrade from pentium4 to pentium3? Dhruba Bandopadhyay
2003-03-06 12:34 ` Paul de Vrieze [this message]
2003-03-06 22:17 ` Martin Schlemmer

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=200303061335.06100.gentoo-user@devrieze.net \
    --to=gentoo-user@devrieze.net \
    --cc=gentoo-dev@gentoo.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