public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paolo Carlini <paolo.carlini@oracle.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Jakub Jelinek <jakub@redhat.com>,
	"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
	  Jason Merrill <jason@redhat.com>
Subject: Re: Why is __i686 undefined for x86_64 -m32 (in mainline)
Date: Tue, 16 Mar 2010 21:34:00 -0000	[thread overview]
Message-ID: <4B9FF88F.4010609@oracle.com> (raw)
In-Reply-To: <6dc9ffc81003161420q702022a3mb95a0ca6e6709a7d@mail.gmail.com>

On 03/16/2010 10:20 PM, H.J. Lu wrote:
> That is not true. The new -m32 default ISA on x86-64 is i686 + MMX + SSE + SSE2.
> It is Pentium 4, not i686.  For historical reason, we define __k8
> instead of __pentium4.
>   
Ah, ok, this is what I was missing! We have *more* than i686. Thus I can
check for __k8.

Thanks again,
Paolo.

  reply	other threads:[~2010-03-16 21:31 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4B9FDCC1.2080201@oracle.com>
2010-03-16 20:00 ` H.J. Lu
2010-03-16 20:40   ` Paolo Carlini
2010-03-16 20:53     ` H.J. Lu
2010-03-16 20:58       ` Paolo Carlini
2010-03-16 21:03         ` Jakub Jelinek
2010-03-16 21:06           ` Paolo Carlini
2010-03-16 21:06             ` H.J. Lu
2010-03-16 21:08               ` H.J. Lu
2010-03-16 21:15           ` H.J. Lu
2010-03-16 21:21             ` Paolo Carlini
2010-03-16 21:31               ` H.J. Lu
2010-03-16 21:34                 ` Paolo Carlini [this message]
2010-03-16 21:36                   ` H.J. Lu
2010-03-16 22:27                     ` Paolo Carlini
2010-03-16 22:32                       ` H.J. Lu
2010-03-16 22:36                         ` Paolo Carlini
2010-03-16 22:39                           ` H.J. Lu
2010-03-16 22:57                             ` Paolo Carlini
2010-03-16 23:11                               ` H.J. Lu
2010-03-17  3:27                                 ` Paolo Carlini
2010-03-16 19:53 Paolo Carlini

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=4B9FF88F.4010609@oracle.com \
    --to=paolo.carlini@oracle.com \
    --cc=gcc@gcc.gnu.org \
    --cc=hjl.tools@gmail.com \
    --cc=jakub@redhat.com \
    --cc=jason@redhat.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).