public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "boger at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/66870] split stack issues on ppc64le and ppc64
Date: Wed, 28 Oct 2015 16:01:00 -0000	[thread overview]
Message-ID: <bug-66870-4-SvTt9eB7fY@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 #33 from boger at gcc dot gnu.org ---
Author: boger
Date: Wed Oct 28 16:00:46 2015
New Revision: 229493

URL: https://gcc.gnu.org/viewcvs?rev=229493&root=gcc&view=rev
Log:
Backport of r229009

PR66870 PowerPC64 Enable gold linker with split stack

A powerpc-linux/powerpc64-linux biarch compiler can default to either
-m32 or -m64, and we need to notice both -m32 and -m64 on the gccgo
command line.  It's also possible to build a -m64 only compiler, so in
that case we can define TARGET_CAN_SPLIT_STACK.

gcc/
        PR go/66870
        * config/rs6000/sysv4.h (TARGET_CAN_SPLIT_STACK_64BIT): Don't define.
        * config/rs6000/linux64.h (TARGET_CAN_SPLIT_STACK): Define.
        (TARGET_CAN_SPLIT_STACK_64BIT): Define.
gcc/go/
        PR go/66870
        * gospec.c (saw_opt_m32): Rename to..
        (is_m64): ..this, initialised by TARGET_CAN_SPLIT_STACK_64BIT.
        Update uses.
        (lang_specific_driver): Set is_m64 if OPT_m64, clear if OPT_m32. 

Modified:
    branches/ibm/gcc-5-branch/gcc/config/rs6000/linux64.h
    branches/ibm/gcc-5-branch/gcc/config/rs6000/sysv4.h
    branches/ibm/gcc-5-branch/gcc/go/gospec.c


      parent reply	other threads:[~2015-10-28 16:01 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
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 airs dot com
2015-10-01 14:44 ` ian at gcc dot gnu.org
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 [this message]

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-SvTt9eB7fY@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).