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: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Why is __i686 undefined for x86_64 -m32 (in mainline)
Date: Tue, 16 Mar 2010 22:36:00 -0000	[thread overview]
Message-ID: <4BA006FA.2040203@oracle.com> (raw)
In-Reply-To: <6dc9ffc81003161527i19986a2dodebc53066c7f0904@mail.gmail.com>

On 03/16/2010 11:27 PM, H.J. Lu wrote:
> Do you care about -march=core2?
Ok, thanks, let's check __core2 too, but really, I don't want to fiddle
too much with these macros in the 4.5.0 timeframe. This is code for
parallel-mode which really is tailored by and large to modern 64-bit
machines. For further enhancements we have libstdc++/34106.

Paolo.

  reply	other threads:[~2010-03-16 22:32 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
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 [this message]
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=4BA006FA.2040203@oracle.com \
    --to=paolo.carlini@oracle.com \
    --cc=gcc@gcc.gnu.org \
    --cc=hjl.tools@gmail.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).