From: Benno Evers <benno.martin.evers@googlemail.com>
To: Iain Sandoe <iain@sandoe.co.uk>
Cc: Jason Merrill <jason@redhat.com>, GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH RFC] Fix ICE due to shared BLOCK node in coroutine generation [PR103328]
Date: Wed, 30 Mar 2022 15:06:31 +0200 [thread overview]
Message-ID: <CAEQVFRGxxFuPmvtkuHmBiiKBrNBGdD_uu_hK1FXb+xFgx3bdng@mail.gmail.com> (raw)
In-Reply-To: <4B530314-E417-418C-9F4F-0F12F3C51A42@sandoe.co.uk>
> Benno, do you have write access?
>
> If not I can take care of this for you if you like?
I do not have write access, so that would be great. I've sent a new
version with added Changelog entries and your test to the list.
Do you think there's a chance to get this patch backported to gcc 10?
That's where we originally encountered the bug, and it proved to be a
show-stopper for our coroutine experiments because we could not find a
deterministic workaround.
Best regards,
Benno
prev parent reply other threads:[~2022-03-30 13:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 11:37 Benno Evers
2022-03-27 1:33 ` Jason Merrill
2022-03-28 6:57 ` Iain Sandoe
2022-03-30 13:06 ` Benno Evers [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=CAEQVFRGxxFuPmvtkuHmBiiKBrNBGdD_uu_hK1FXb+xFgx3bdng@mail.gmail.com \
--to=benno.martin.evers@googlemail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iain@sandoe.co.uk \
--cc=jason@redhat.com \
/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).