public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Richard Biener <rguenther@suse.de>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] bitint: Fix up adjustment of large/huge _BitInt arguments of returns_twice calls [PR113466]
Date: Thu, 14 Mar 2024 09:53:35 +0100	[thread overview]
Message-ID: <ZfK7D/6pK+kwBDpR@tucnak> (raw)
In-Reply-To: <r79s4559-s58r-rs15-qns7-oopros2r6199@fhfr.qr>

On Thu, Mar 14, 2024 at 09:48:45AM +0100, Richard Biener wrote:
> Ugh.  OK, but I wonder whether we might want to simply delay
> fixing the CFG for inserts before returns-twice?  Would that make
> things less ugly?

You mean in lower_call just remember if we added anything before
ECF_RETURNS_TWICE call (or say add such stmt into a vector) and
then fix it up before the end of the pass?
I can certainly try that and see what is shorter/more maintainable.

	Jakub


  reply	other threads:[~2024-03-14  8:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-14  8:28 Jakub Jelinek
2024-03-14  8:48 ` Richard Biener
2024-03-14  8:53   ` Jakub Jelinek [this message]
2024-03-14  8:59     ` Richard Biener
2024-03-14 10:42       ` [PATCH] bitint, v2: " Jakub Jelinek
2024-03-14 11:52         ` Richard Biener

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=ZfK7D/6pK+kwBDpR@tucnak \
    --to=jakub@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=rguenther@suse.de \
    /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).