From: "H.J. Lu" <hjl.tools@gmail.com>
To: Torvald Riegel <triegel@redhat.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Richard Henderson <rth@redhat.com>
Subject: Re: [trans-mem] Use __x86_64__ instead of __LP64__.
Date: Mon, 22 Aug 2011 14:12:00 -0000 [thread overview]
Message-ID: <CAMe9rOr7TqNrNkO_57e-jNSNkCRcEahuTzFa-FhufKEwwUbuWQ@mail.gmail.com> (raw)
In-Reply-To: <1314006155.3533.2576.camel@triegel.csb>
On Mon, Aug 22, 2011 at 2:42 AM, Torvald Riegel <triegel@redhat.com> wrote:
> Use __x86_64__ instead of __LP64__ in setjmp/longjmp and TLS
> definitions.
>
> H.J.: Is that sufficient for x32, or do we need entirely different code?
> If so, can you please provide the required changes?
>
I need to take a look.
Thanks.
--
H.J.
next prev parent reply other threads:[~2011-08-22 13:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-22 9:57 Torvald Riegel
2011-08-22 14:12 ` H.J. Lu [this message]
2011-08-23 15:19 ` H.J. Lu
2011-08-23 7:08 ` Richard Henderson
2011-08-23 14:37 ` Torvald Riegel
2011-08-23 18:08 ` Richard Henderson
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=CAMe9rOr7TqNrNkO_57e-jNSNkCRcEahuTzFa-FhufKEwwUbuWQ@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rth@redhat.com \
--cc=triegel@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).