From: Andreas Schwab <schwab@linux-m68k.org>
To: gcc-patches@gcc.gnu.org
Cc: David Edelsohn <dje.gcc@gmail.com>
Subject: Re: [Patch 0/4] PowerPC64 Linux split stack support
Date: Mon, 15 Jun 2015 19:14:00 -0000 [thread overview]
Message-ID: <87k2v4pzn0.fsf@igel.home> (raw)
In-Reply-To: <20150615090333.GF1723@bubble.grove.modra.org> (Alan Modra's message of "Mon, 15 Jun 2015 18:33:33 +0930")
* go-lang.c (go_langhook_init_options_struct): Don't set
x_flag_split_stack.
(go_langhook_post_options): Set it here instead.
---
gcc/go/go-lang.c | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/gcc/go/go-lang.c b/gcc/go/go-lang.c
index ce4dd9b..d952e0f 100644
--- a/gcc/go/go-lang.c
+++ b/gcc/go/go-lang.c
@@ -158,10 +158,6 @@ go_langhook_init_options_struct (struct gcc_options *opts)
opts->x_flag_errno_math = 0;
opts->frontend_set_flag_errno_math = true;
- /* We turn on stack splitting if we can. */
- if (targetm_common.supports_split_stack (false, opts))
- opts->x_flag_split_stack = 1;
-
/* Exceptions are used to handle recovering from panics. */
opts->x_flag_exceptions = 1;
opts->x_flag_non_call_exceptions = 1;
@@ -295,6 +291,11 @@ go_langhook_post_options (const char **pfilename ATTRIBUTE_UNUSED)
&& global_options.x_write_symbols == NO_DEBUG)
global_options.x_write_symbols = PREFERRED_DEBUGGING_TYPE;
+ /* We turn on stack splitting if we can. */
+ if (!global_options_set.x_flag_split_stack
+ && targetm_common.supports_split_stack (false, &global_options))
+ global_options.x_flag_split_stack = 1;
+
/* Returning false means that the backend should be used. */
return false;
}
--
2.4.3
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2015-06-15 18:58 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-18 2:54 Alan Modra
2015-05-18 2:54 ` [PATCH 1/4] rs6000_stack_info changes for -fsplit-stack Alan Modra
2015-05-18 18:08 ` David Edelsohn
2015-05-20 1:45 ` Alan Modra
2015-05-20 13:07 ` David Edelsohn
2015-05-20 13:29 ` Alan Modra
2015-05-18 2:55 ` [PATCH 3/4] split-stack for powerpc64 Alan Modra
2015-05-18 7:05 ` Alan Modra
2015-05-19 12:48 ` Lynn A. Boger
2015-05-20 1:03 ` Alan Modra
2015-05-20 12:14 ` Lynn A. Boger
2015-05-20 12:59 ` David Edelsohn
2015-05-20 16:01 ` Lynn A. Boger
2015-05-19 14:37 ` David Edelsohn
2015-05-21 2:10 ` Alan Modra
2015-05-29 16:09 ` Alan Modra
2015-05-29 17:25 ` David Edelsohn
2015-05-18 2:55 ` [PATCH 2/4] prologue and epilogue tidy and -mno-vrsave bug fix Alan Modra
2015-05-19 14:35 ` David Edelsohn
2015-05-18 3:42 ` [PATCH 4/4] Split-stack arg pointer init refinement Alan Modra
2015-06-13 12:05 ` [Patch 0/4] PowerPC64 Linux split stack support Andreas Schwab
2015-06-15 9:09 ` Alan Modra
2015-06-15 9:51 ` Andreas Schwab
2015-06-15 17:31 ` Andreas Schwab
2015-06-15 17:56 ` Andreas Schwab
2015-06-15 19:14 ` Andreas Schwab [this message]
2015-06-19 13:04 ` Andreas Schwab
2015-07-30 19:23 ` Lynn A. Boger
2015-07-31 0:32 ` Ian Lance Taylor
2015-07-01 14:09 ` Lynn A. Boger
2015-07-01 14:15 ` Andreas Schwab
2015-07-17 12:37 ` 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=87k2v4pzn0.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@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).