From: Richard Biener <richard.guenther@gmail.com>
To: Eric Botcazou <botcazou@adacore.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch] Fix ICE with stack checking emulation at -O2
Date: Fri, 1 Oct 2021 10:43:29 +0200 [thread overview]
Message-ID: <CAFiYyc3E9MkZ3N4DK+jk8Ni7rNs1gcuKqiOCzm=J2w88NBO8yw@mail.gmail.com> (raw)
In-Reply-To: <2078204.irdbgypaU6@fomalhaut>
On Fri, Oct 1, 2021 at 10:30 AM Eric Botcazou <botcazou@adacore.com> wrote:
>
> > OK though I wonder if you could get away with using
> > built_function_type (void_type_node, NULL_TREE); aka
> > a non-prototype void f().
>
> See below.
>
> > Did you track down what changed the requirement?
>
> The new function-abi.cc module, so I'd rather have a correct prototype.
I see, yes that makes sense.
Thanks,
Richard.
> --
> Eric Botcazou
>
>
prev parent reply other threads:[~2021-10-01 8:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 8:16 Eric Botcazou
2021-10-01 8:23 ` Richard Biener
2021-10-01 8:30 ` Eric Botcazou
2021-10-01 8:43 ` Richard Biener [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='CAFiYyc3E9MkZ3N4DK+jk8Ni7rNs1gcuKqiOCzm=J2w88NBO8yw@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=botcazou@adacore.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).