From: "Lynn A. Boger" <laboger@linux.vnet.ibm.com>
To: Matthias Klose <doko@ubuntu.com>, Ian Lance Taylor <iant@golang.org>
Cc: David Edelsohn <dje.gcc@gmail.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
Alan Modra <amodra@gmail.com>
Subject: Re: [PATCH] PR66870 PowerPC64 Enable gold linker with split stack
Date: Thu, 08 Oct 2015 18:56:00 -0000 [thread overview]
Message-ID: <5616BC63.3060307@linux.vnet.ibm.com> (raw)
In-Reply-To: <561556F9.8030802@ubuntu.com>
I think my original fix with linux.h doing the #undef on
TARGET_CAN_SPLIT_STACK_64BIT is the right fix at least
for powerpc-linux-gnu 32 bit only.
It works for powerpc-linux-gnu without multilib and doesn't break
powerpc64-linux-gnu or powerpc64le-linux-gnu.
Can you tell me how you are configuring the multilib build that defaults
to powerpc-linux-gnu and how it
fails? Maybe there is another problem for that combination.
As David noted, the use of TARGET_64BIT or TARGET_POWERPC64 won't work
for this #define.
On 10/07/2015 12:31 PM, Matthias Klose wrote:
> On 07.10.2015 17:36, Lynn A. Boger wrote:
>> Pretty sure this is the fix, but still doing some testing.
>
> linux.h isn't included for multilib enabled builds defaulting to
> powerpc-linux-gnu, I am currently testing
>
> --- gcc/config/rs6000/sysv4.h (revision 228571)
> +++ gcc/config/rs6000/sysv4.h (working copy)
> @@ -943,8 +943,9 @@
> /* On ppc64 and ppc64le, split stack is only support for
> 64 bit. */
> #undef TARGET_CAN_SPLIT_STACK_64BIT
> -#if TARGET_GLIBC_MAJOR > 2 \
> - || (TARGET_GLIBC_MAJOR == 2 && TARGET_GLIBC_MINOR >= 18)
> +#if TARGET_64BIT \
> + && (TARGET_GLIBC_MAJOR > 2 \
> + || (TARGET_GLIBC_MAJOR == 2 && TARGET_GLIBC_MINOR >= 18))
> #define TARGET_CAN_SPLIT_STACK_64BIT
> #endif
>
>
>
>
next prev parent reply other threads:[~2015-10-08 18:56 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 21:14 Lynn A. Boger
2015-08-19 19:37 ` Matthias Klose
2015-08-19 19:42 ` David Edelsohn
2015-08-19 22:07 ` Lynn A. Boger
2015-08-20 0:01 ` Lynn A. Boger
2015-08-27 21:37 ` Lynn A. Boger
2015-09-15 16:50 ` Ian Lance Taylor
2015-09-15 18:21 ` David Edelsohn
2015-09-15 18:31 ` Lynn A. Boger
2015-09-15 20:04 ` Ian Lance Taylor
2015-09-17 19:15 ` Lynn A. Boger
2015-09-18 12:59 ` David Edelsohn
2015-09-30 12:46 ` Lynn A. Boger
[not found] ` <CAOyqgcVA_zhivM0+qRFk9bDT42Sot-HX95M1NtZjLVphZy_0vg@mail.gmail.com>
2015-10-03 18:31 ` Matthias Klose
[not found] ` <56153C00.2000209@linux.vnet.ibm.com>
2015-10-07 17:04 ` Ian Lance Taylor
2015-10-07 17:25 ` David Edelsohn
2015-10-07 17:31 ` Matthias Klose
[not found] ` <5615746C.3030509@linux.vnet.ibm.com>
2015-10-07 21:58 ` David Edelsohn
2015-10-08 18:56 ` Lynn A. Boger [this message]
2015-10-08 20:46 ` Matthias Klose
2015-10-09 20:17 ` Lynn A. Boger
2015-10-10 14:00 ` David Edelsohn
2015-10-10 21:03 ` Matthias Klose
2015-10-10 21:25 ` Andreas Schwab
2015-10-11 13:07 ` Alan Modra
2015-10-11 14:43 ` Andreas Schwab
2015-10-11 18:29 ` Ian Lance Taylor
2015-10-11 23:19 ` Alan Modra
2015-10-12 15:15 ` Lynn A. Boger
2015-10-12 22:53 ` Alan Modra
2015-10-13 11:27 ` Matthias Klose
2015-10-15 18:40 ` David Edelsohn
2015-10-15 19:57 ` Lynn A. Boger
2015-10-17 0:37 ` Ian Lance Taylor
2015-08-25 23:05 ` Ian Lance Taylor
2015-08-26 14:01 ` Lynn A. Boger
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=5616BC63.3060307@linux.vnet.ibm.com \
--to=laboger@linux.vnet.ibm.com \
--cc=amodra@gmail.com \
--cc=dje.gcc@gmail.com \
--cc=doko@ubuntu.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iant@golang.org \
/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).