From: Bill Schmidt <wschmidt@linux.vnet.ibm.com>
To: Eric Botcazou <ebotcazou@adacore.com>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
GCC Patches <gcc-patches@gcc.gnu.org>,
David Edelsohn <dje.gcc@gmail.com>
Subject: Re: [PATCH, rs6000] Fix PR72827 (ada bootstrap failure)
Date: Wed, 31 Aug 2016 16:13:00 -0000 [thread overview]
Message-ID: <20340771-3D13-4446-8340-7D2D1F63CC10@linux.vnet.ibm.com> (raw)
In-Reply-To: <2780281.YOzxdaXCH3@arcturus.home>
> On Aug 31, 2016, at 10:31 AM, Eric Botcazou <ebotcazou@adacore.com> wrote:
>
>> I'm not sure I'm the right person to do that, as I don't really have any
>> familiarity with the DSE code. I can't even prove to myself that this code
>> is alloca-safe; it doesn't look like it.
>
> No FUD, please ;-) The code is alloca-safe, alloca is about moving the stack
> pointer, not the frame pointer. The compiler wouldn't be able to compile a
> simple Ada program with optimization enabled if that wasn't the case.
Heh, not my intent. :) The alloca code was hiding off in cselib anyway...as
I said, I don't have any familiarity here...
>
> --
> Eric Botcazou
>
next prev parent reply other threads:[~2016-08-31 16:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 1:24 Bill Schmidt
2016-08-31 6:20 ` Segher Boessenkool
2016-08-31 7:08 ` Eric Botcazou
2016-08-31 9:07 ` Segher Boessenkool
2016-09-06 21:31 ` Jeff Law
2016-09-06 23:02 ` Segher Boessenkool
2016-09-07 0:10 ` Jeff Law
2016-08-31 14:00 ` Bill Schmidt
2016-08-31 15:31 ` Eric Botcazou
2016-08-31 16:13 ` Bill Schmidt [this message]
2016-08-31 20:07 ` Bill Schmidt
2016-09-01 2:15 ` [PATCH v2, " Bill Schmidt
2016-09-01 7:21 ` Eric Botcazou
2016-09-01 14:32 ` Segher Boessenkool
2016-09-01 14:44 ` Bill Schmidt
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=20340771-3D13-4446-8340-7D2D1F63CC10@linux.vnet.ibm.com \
--to=wschmidt@linux.vnet.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--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).