From: Uros Bizjak <ubizjak@gmail.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: gcc-patches@gcc.gnu.org,
"Joseph S. Myers" <joseph@codesourcery.com>,
Paolo Bonzini <bonzini@gnu.org>
Subject: Re: PATCH [1/n] X32: Add initial -x32 support
Date: Tue, 05 Jul 2011 20:07:00 -0000 [thread overview]
Message-ID: <CAFULd4Zj2_YEygNMOZqO5XwZQD484WP-7pxofaCmtB6MyzJVoQ@mail.gmail.com> (raw)
In-Reply-To: <CAMe9rOrCWLnyO=hcK2CHajBEoj8XQmx7mCPW-22g87uR3oXxmw@mail.gmail.com>
On Tue, Jul 5, 2011 at 8:49 PM, H.J. Lu <hjl.tools@gmail.com> wrote:
>> #undef LINK_SPEC
>> #define LINK_SPEC "%{" SPEC_64 ":-m " GNU_USER_LINK_EMULATION64 "} \
>> %{" SPEC_32 ":-m " GNU_USER_LINK_EMULATION32 "} \
>> + %{" SPEC_X32 ":-m " GNU_USER_LINK_EMULATIONX32 "} \
>> %{shared:-shared} \
>> %{!shared: \
>> %{!static: \
>> %{rdynamic:-export-dynamic} \
>> %{" SPEC_32 ":-dynamic-linker " GNU_USER_DYNAMIC_LINKER32 "} \
>> - %{" SPEC_64 ":-dynamic-linker " GNU_USER_DYNAMIC_LINKER64 "}} \
>> + %{" SPEC_64 ":-dynamic-linker " GNU_USER_DYNAMIC_LINKER64 "} \
>> + %{" SPEC_X32 ":-dynamic-linker " GNU_USER_DYNAMIC_LINKERX32 "}} \
>> %{static:-static}}"
>>
>> On the border of bikesheding, GNU_USER_LINK_EMULATION64_X32 and
>> GNU_USER_DYNAMIC_LINKER64_X32 sounds better to me.
>>
>> Same with the below:
>>
>> +#define GLIBC_DYNAMIC_LINKERX32 "/libx32/ld-linux-x32.so.2"
>> +#define UCLIBC_DYNAMIC_LINKERX32 "/lib/ldx32-uClibc.so.0"
>> +#define BIONIC_DYNAMIC_LINKERX32 "/system/bin/linkerx32"
>>
>> +++ b/gcc/config/i386/t-linux-x32
>>
>> Please rename above file to t-linux64-x32.
>
> X32 is the name of the psABI:
>
> https://sites.google.com/site/x32abi/
>
> We have -mx32, -m32 and -m64 command line options and
> There are macros like TARGET_X32. I'd like to be consistent
> and avoid "64" when referring to x32 if possible. But I won't
> insist. Please let me know that you really won't like x32 without
> 64.
I would like to point out that the base target is in fact 64 bit and a
subtarget is x32, so ...64-x32. I could read this as 64bit target with
x32 ABI. Perhaps we will have 64-xxx or whatever different ABIs that
all apply to the same 64bit hardware.
These are my personal preferences, so I will leave the final decision
about names of defines and file names to you.
Thanks,
Uros.
next prev parent reply other threads:[~2011-07-05 19:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-05 19:55 PATCH [1/n]: " H.J. Lu
2011-06-06 15:47 ` Uros Bizjak
2011-06-07 15:47 ` Joseph S. Myers
2011-06-07 18:54 ` H.J. Lu
2011-06-07 19:19 ` Joseph S. Myers
2011-06-07 15:59 ` Joseph S. Myers
2011-06-07 19:11 ` H.J. Lu
2011-06-07 19:20 ` Joseph S. Myers
2011-06-07 22:02 ` H.J. Lu
2011-06-14 17:52 ` H.J. Lu
2011-07-05 14:42 ` PATCH [1/n] X32: " H.J. Lu
2011-07-05 15:21 ` Uros Bizjak
2011-07-05 17:59 ` H.J. Lu
2011-07-05 18:18 ` Uros Bizjak
2011-07-05 19:09 ` H.J. Lu
2011-07-05 19:09 ` Joseph S. Myers
2011-07-05 20:07 ` Uros Bizjak [this message]
2011-07-06 14:50 ` H.J. Lu
2011-07-06 15:03 ` Richard Guenther
2011-07-06 16:40 ` H.J. Lu
2011-07-07 13:03 ` H.J. Lu
2011-07-07 13:08 ` Uros Bizjak
2011-07-07 13:27 ` Paolo Bonzini
2011-07-07 15:10 ` H.J. Lu
2011-07-07 15:14 ` Uros Bizjak
2011-07-07 15:38 ` Paolo Bonzini
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=CAFULd4Zj2_YEygNMOZqO5XwZQD484WP-7pxofaCmtB6MyzJVoQ@mail.gmail.com \
--to=ubizjak@gmail.com \
--cc=bonzini@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=joseph@codesourcery.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).