public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/112781] [13/14 regression] internal error on function call returning extension of limited interface
Date: Tue, 05 Dec 2023 11:39:10 +0000 [thread overview]
Message-ID: <bug-112781-4-xyOzoTEsmQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112781-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112781
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[13/14 regression] ICE in |[13/14 regression] internal
|generic instantiation |error on function call
| |returning extension of
| |limited interface
--- Comment #3 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
The testcase triggers 3 different assertion failures, the first 2 are benign
but not the third, which leads to the wrong code with GCC 13.x (the workaround
for the latter is to remove the "limited" keyword everywhere).
next prev parent reply other threads:[~2023-12-05 11:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 12:27 [Bug ada/112781] New: [13?/14 regression] ICE in generic instantiation simon at pushface dot org
2023-11-30 13:57 ` [Bug ada/112781] " rguenth at gcc dot gnu.org
2023-12-04 17:24 ` [Bug ada/112781] [13/14 " ebotcazou at gcc dot gnu.org
2023-12-05 0:51 ` ebotcazou at gcc dot gnu.org
2023-12-05 11:39 ` ebotcazou at gcc dot gnu.org [this message]
2024-01-09 9:49 ` [Bug ada/112781] [13/14 regression] internal error on function call returning extension of limited interface cvs-commit at gcc dot gnu.org
2024-01-09 9:50 ` cvs-commit at gcc dot gnu.org
2024-01-09 10:07 ` cvs-commit at gcc dot gnu.org
2024-01-09 10:14 ` cvs-commit at gcc dot gnu.org
2024-01-09 10:14 ` ebotcazou at gcc dot gnu.org
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-112781-4-xyOzoTEsmQ@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).