public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "boger at us dot ibm.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/66870] split stack issues on ppc64le and ppc64
Date: Wed, 05 Aug 2015 13:44:00 -0000	[thread overview]
Message-ID: <bug-66870-4-jMhEvfn4yk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66870-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66870

--- Comment #17 from boger at us dot ibm.com ---
Created attachment 36132
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36132&action=edit
Configure gold linker with split stack if available

Attaching my patch to detect for split stack support within the gold linker
that is available by the gcc build, and then use it with gccgo compiles.  Here
are the steps:
- When configuring gcc, check for split stack support in the gold linker either
identified as the linker to use in the gcc build or found in the path at build
time.  This check currently only works on ppc64le; I couldn't get it to fail on
ppc64 even with older (2.24) gold linkers.  Not sure what might be wanted for
other targets.  If the support is there then HAVE_LD_GOLD_SUPPORTS_SPLIT_STACK
is defined.
- Modify the check in libgo configure to detect that the gold linker used with
the gccgo that was just built supports split stack, defining
LINKER_SUPPORTS_SPLIT_STACK if it is.
- Add -fuse-ld=gold to the linker spec if HAVE_LD_GOLD_SUPPORTS_SPLIT_STACK is
defined (not for m32).
- Define TARGET_CAN_SPLIT_STACK for Power targets if the glibc level is
correct.  This is needed by go/gospec.c to enable the -fsplit-stack option when
linking.  

Comments?


  parent reply	other threads:[~2015-08-05 13:44 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-14 14:31 [Bug go/66870] New: " boger at us dot ibm.com
2015-07-14 15:02 ` [Bug go/66870] " ian at airs dot com
2015-07-14 15:52 ` boger at us dot ibm.com
2015-07-14 17:53 ` ian at airs dot com
2015-07-14 20:11 ` schwab@linux-m68k.org
2015-07-14 20:31 ` boger at us dot ibm.com
2015-07-14 22:36 ` schwab@linux-m68k.org
2015-07-15  3:43 ` amodra at gmail dot com
2015-07-15 16:02 ` boger at us dot ibm.com
2015-07-15 16:08 ` boger at us dot ibm.com
2015-07-16 19:29 ` boger at us dot ibm.com
2015-07-17  9:50 ` amodra at gmail dot com
2015-07-17 12:59 ` amodra at gmail dot com
2015-07-22 17:46 ` boger at us dot ibm.com
2015-07-23 12:56 ` boger at us dot ibm.com
2015-07-30 20:42 ` boger at us dot ibm.com
2015-07-31 14:06 ` amodra at gcc dot gnu.org
2015-08-05 13:44 ` boger at us dot ibm.com [this message]
2015-08-05 14:48 ` ian at airs dot com
2015-08-05 18:07 ` boger at gcc dot gnu.org
2015-08-13  5:25 ` amodra at gcc dot gnu.org
2015-09-30 23:06 ` ian at gcc dot gnu.org
2015-10-01 12:38 ` boger at us dot ibm.com
2015-10-01 12:40 ` schwab@linux-m68k.org
2015-10-01 13:40 ` ian at airs dot com
2015-10-01 14:03 ` boger at us dot ibm.com
2015-10-01 14:44 ` ian at gcc dot gnu.org
2015-10-01 14:44 ` ian at airs dot com
2015-10-08 19:22 ` boger at gcc dot gnu.org
2015-10-19 23:51 ` amodra at gcc dot gnu.org
2015-10-28 16:01 ` boger at gcc dot gnu.org

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=bug-66870-4-jMhEvfn4yk@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).