public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Sandiford <richard.sandiford@linaro.org>
To: Mike Stump <mikestump@comcast.net>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: Remove the frame size argument from function_prologue/epilogue
Date: Wed, 23 Aug 2017 09:20:00 -0000	[thread overview]
Message-ID: <87h8wybtxf.fsf@linaro.org> (raw)
In-Reply-To: <CF8489CE-93B4-47AB-89E2-C78EF19818BE@comcast.net> (Mike Stump's	message of "Tue, 22 Aug 2017 10:49:17 -0700")

Mike Stump <mikestump@comcast.net> writes:
> On Aug 21, 2017, at 4:12 AM, Richard Sandiford
> <richard.sandiford@linaro.org> wrote:
>> 
>> Later patches will add support for frame sizes that are a run-time
>> invariant but not a compile-time constant.
>
> I'm assuming dwarf and C++ exceptions will remain working.  :-)

Sure :-)  The vector length is represented as a DWARF pseudo register.

      reply	other threads:[~2017-08-23  7:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-21 12:22 Richard Sandiford
2017-08-21 13:04 ` Richard Biener
2017-08-22 18:47 ` Mike Stump
2017-08-23  9:20   ` Richard Sandiford [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=87h8wybtxf.fsf@linaro.org \
    --to=richard.sandiford@linaro.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=mikestump@comcast.net \
    /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).