From: Segher Boessenkool <segher@kernel.crashing.org>
To: Olivier Hainque <hainque@adacore.com>
Cc: Richard Henderson <rth@redhat.com>, Alan Modra <amodra@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: rs6000 stack_tie mishap again
Date: Fri, 08 Apr 2016 15:37:00 -0000 [thread overview]
Message-ID: <20160408153726.GB26837@gate.crashing.org> (raw)
In-Reply-To: <2408A462-EA11-4E44-97F7-DB9DF75FCCE2@adacore.com>
On Fri, Apr 08, 2016 at 10:24:50AM +0200, Olivier Hainque wrote:
> > But I expect for stage4, the best solution is to strengthen the stack_tie pattern to block all memory. Early scheduling of the stack frame deallocation (a simple logic insn) can't really be that important to performance.
>
> My feeling as well. At least, it can't be important enough to warrant
> a sustained exposure to the kind of bug we're discussing here.
Is it a regression? Changing this in stage 4, and this late in stage 4,
is super invasive. Wrt performance, well, I'd like to see numbers :-/
Segher
next prev parent reply other threads:[~2016-04-08 15:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 16:24 Olivier Hainque
2016-03-24 7:51 ` Alan Modra
2016-03-24 10:32 ` Olivier Hainque
2016-03-24 17:00 ` Jeff Law
2016-03-28 19:58 ` Richard Henderson
2016-04-08 8:25 ` Olivier Hainque
2016-04-08 15:37 ` Segher Boessenkool [this message]
2016-04-08 16:01 ` Olivier Hainque
2016-04-11 10:15 ` Olivier Hainque
2016-04-14 15:47 ` Andreas Krebbel
2016-04-14 16:50 ` Jeff Law
2016-04-14 17:10 ` Olivier Hainque
2016-04-15 4:37 ` Andreas Krebbel
2016-04-15 7:43 ` Olivier Hainque
2016-04-15 16:42 ` Jeff Law
2016-04-15 17:05 ` Olivier Hainque
2016-04-15 17:26 ` Segher Boessenkool
2016-04-14 22:42 ` Segher Boessenkool
2016-04-15 15:17 ` Olivier Hainque
2016-03-28 4:48 ` Segher Boessenkool
2016-03-28 11:23 ` Olivier Hainque
2016-03-28 12:44 ` Segher Boessenkool
2016-03-30 9:40 ` Olivier Hainque
2016-03-30 15:15 ` Alan Modra
2016-03-23 17:42 David Edelsohn
2016-03-24 8:17 ` Alan Modra
2016-03-24 10:17 ` Olivier Hainque
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=20160408153726.GB26837@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=amodra@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hainque@adacore.com \
--cc=rth@redhat.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).