From: Uros Bizjak <ubizjak@gmail.com>
To: gcc-patches@gcc.gnu.org
Cc: "H.J. Lu" <hjl.tools@gmail.com>
Subject: Re: PATCH: Define TRY_EMPTY_VM_SPACE for Linux/x32
Date: Wed, 04 Apr 2012 18:08:00 -0000 [thread overview]
Message-ID: <CAFULd4afnrbE0vzrBE6v24GJkjLv8hB13YzpFTvTPb=Coy5pZw@mail.gmail.com> (raw)
Hello!
> This patch defines TRY_EMPTY_VM_SPACE for Linux/x32. Tested on Linux/x32.
> OK for trunk?
>
> 2012-04-03 H.J. Lu <hongjiu.lu@intel.com>
>
> * config/host-linux.c (TRY_EMPTY_VM_SPACE): Defined to
> 0x60000000 for x32.
I think we can simply check for __LP64__, without version check, as is
the case with SPARC and MIPS targets.
Uros.
Index: host-linux.c
===================================================================
--- host-linux.c (revision 186141)
+++ host-linux.c (working copy)
@@ -68,8 +68,10 @@
# define TRY_EMPTY_VM_SPACE 0x10000000000
#elif defined(__ia64)
# define TRY_EMPTY_VM_SPACE 0x2000000100000000
+#elif defined(__x86_64) && defined(__LP64__)
+# define TRY_EMPTY_VM_SPACE 0x1000000000
#elif defined(__x86_64)
-# define TRY_EMPTY_VM_SPACE 0x1000000000
+# define TRY_EMPTY_VM_SPACE 0x60000000
#elif defined(__i386)
# define TRY_EMPTY_VM_SPACE 0x60000000
#elif defined(__powerpc__)
next reply other threads:[~2012-04-04 18:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-04 18:08 Uros Bizjak [this message]
2012-04-04 18:47 ` H.J. Lu
2012-04-04 18:51 ` Uros Bizjak
2012-04-04 18:53 ` Andrew Pinski
2012-04-04 18:57 ` H.J. Lu
2012-04-05 13:28 ` H.J. Lu
2012-04-05 15:36 ` Uros Bizjak
2012-04-05 15:58 ` H.J. Lu
2012-04-10 14:41 ` H.J. Lu
2012-04-11 19:40 ` H.J. Lu
-- strict thread matches above, loose matches on Subject: below --
2012-04-04 1:05 H.J. Lu
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='CAFULd4afnrbE0vzrBE6v24GJkjLv8hB13YzpFTvTPb=Coy5pZw@mail.gmail.com' \
--to=ubizjak@gmail.com \
--cc=gcc-patches@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).