public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@gentoo.org>
To: Gentoo-Dev <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] Gcc 3.2.3+ & Pentium4 cflags
Date: 26 May 2003 22:24:17 +0200	[thread overview]
Message-ID: <1053980656.12234.38.camel@nosferatu.lan> (raw)
In-Reply-To: <1053937459.1579.5.camel@wolf.codewordt.co.uk>

[-- Attachment #1: Type: text/plain, Size: 1058 bytes --]

On Mon, 2003-05-26 at 10:24, Dhruba Bandopadhyay wrote:
> Hello
> 
> Portage 2.0.48 came with the following warning.
> 
> # CRITICAL WARNINGS:
> ****************************************************** #
> # ATHLON-4 will generate invalid SSE  instructions; use 'athlon'  
> instead. #
> # PENTIUM4 will generate invalid SSE2 instructions; use 'pentium3'
> instead. #
> #
> ************************************************************************* 
> However, now that gcc 3.2.3 is on ~x86 I would just like to seek the
> affirmation of the devs that the new gcc does resolve these bugs before
> I move from -march=pentium3 to pentium4.  Is it now safe to use p4 by
> recommendation?
> 
> Out of curiousity how about athlon-4?
> 

For pentium4 some of the bugs seem to be fixed.  I have not have the
chance to check them all yet (and anyhow already getting things
ready for gcc-3.3).

As for athlon-4 ... I have no idea.


-- 

Martin Schlemmer
Gentoo Linux Developer, Desktop/System Team Developer
Cape Town, South Africa



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2003-05-26 20:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-26  8:24 [gentoo-dev] Gcc 3.2.3+ & Pentium4 cflags Dhruba Bandopadhyay
2003-05-26 20:24 ` Martin Schlemmer [this message]

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=1053980656.12234.38.camel@nosferatu.lan \
    --to=azarah@gentoo.org \
    --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