public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "lebedev.k.m at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/101994] go1: internal compiler error: in return_statement, at go/go-gcc.cc:2318
Date: Mon, 30 Aug 2021 06:29:16 +0000 [thread overview]
Message-ID: <bug-101994-4-5M1t9ZuZlB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101994-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101994
--- Comment #3 from Konstantin Lebedev <lebedev.k.m at gmail dot com> ---
(In reply to Ian Lance Taylor from comment #2)
> Fix is https://golang.org/cl/343873. Test case is
> https://golang.org/cl/343874.
Thank you very much
Great job
next prev parent reply other threads:[~2021-08-30 6:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-20 8:29 [Bug go/101994] New: " lebedev.k.m at gmail dot com
2021-08-20 8:32 ` [Bug go/101994] " lebedev.k.m at gmail dot com
2021-08-20 18:37 ` ian at airs dot com
2021-08-30 6:29 ` lebedev.k.m at gmail dot com [this message]
2021-09-11 21:20 ` cvs-commit at gcc dot gnu.org
2021-09-11 21:21 ` ian at airs dot com
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=bug-101994-4-5M1t9ZuZlB@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).