From: Olivier Hainque <hainque@adacore.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Olivier Hainque <hainque@adacore.com>,
Alan Modra <amodra@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Richard Henderson <rth@redhat.com>
Subject: Re: rs6000 stack_tie mishap again
Date: Fri, 15 Apr 2016 15:17:00 -0000 [thread overview]
Message-ID: <F1DDD432-BF81-49B5-B902-085729602131@adacore.com> (raw)
In-Reply-To: <20160414224207.GA25665@gate.crashing.org>
> On Apr 15, 2016, at 00:42 , Segher Boessenkool <segher@kernel.crashing.org> wrote:
>
>>
>> Something like the attached patch, at least for next stage1 until the
>> more general issue is sorted out ?
>
> It's a bit heavy; as a workaround, we may want this clobber in the stack
> deallocation in the epilogue, but not in all other places stack_tie is
> used.
OK, I can add an epilogue_p argument or something like that.
> And for stage 1 we do not really want a workaround, we want to fix the
> actual problem ;-)
Sure. It might take some time though, and we might want
a workaround in the interim. Maintainers' call I suppose :)
next prev parent reply other threads:[~2016-04-15 15:17 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
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 [this message]
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=F1DDD432-BF81-49B5-B902-085729602131@adacore.com \
--to=hainque@adacore.com \
--cc=amodra@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rth@redhat.com \
--cc=segher@kernel.crashing.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).