public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dhruba Bandopadhyay <dhruba@codewordt.co.uk>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Gcc 3.2.3+ & Pentium4 cflags
Date: 26 May 2003 09:24:20 +0100	[thread overview]
Message-ID: <1053937459.1579.5.camel@wolf.codewordt.co.uk> (raw)

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?

Many thanks


--
gentoo-dev@gentoo.org mailing list


             reply	other threads:[~2003-05-26  8:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-26  8:24 Dhruba Bandopadhyay [this message]
2003-05-26 20:24 ` [gentoo-dev] Gcc 3.2.3+ & Pentium4 cflags 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=1053937459.1579.5.camel@wolf.codewordt.co.uk \
    --to=dhruba@codewordt.co.uk \
    --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