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/111434] [13/14 regression] infinite loop with limited with clauses Date: Sun, 24 Sep 2023 21:41:13 +0000 [thread overview] Message-ID: <bug-111434-4-AYG0Wpv3Pc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111434-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111434 Eric Botcazou <ebotcazou at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2023-09-24 Summary|Infinite loop with limited |[13/14 regression] infinite |withs? |loop with limited with | |clauses Status|UNCONFIRMED |NEW CC| |ebotcazou at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #1 from Eric Botcazou <ebotcazou at gcc dot gnu.org> --- Confirmed, it's an assertion failure on the mainline: eric@fomalhaut:~/build/gcc/native/tmp>gcc -c pyside6-qtcore.adb +===========================GNAT BUG DETECTED==============================+ | 14.0.0 20230918 (experimental) [master r14-4085-g93996cfb308] (x86_64-suse-linux) | | Assert_Failure sem_ch10.adb:5305 | | Error detected at pyside6-qtcore-qtmsgtype.ads:2:23 | | Compiling pyside6-qtcore.adb |
next prev parent reply other threads:[~2023-09-24 21:41 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-16 14:20 [Bug ada/111434] New: Infinite loop with limited withs? p.p11 at orange dot fr 2023-09-24 21:41 ` ebotcazou at gcc dot gnu.org [this message] 2023-09-24 21:53 ` [Bug ada/111434] [13/14 regression] infinite loop with limited with clauses ebotcazou at gcc dot gnu.org 2023-10-10 12:14 ` [Bug ada/111434] [13/14 regression] infinite loop with multiple " cvs-commit at gcc dot gnu.org 2023-10-10 15:12 ` cvs-commit at gcc dot gnu.org 2023-10-10 15:13 ` 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-111434-4-AYG0Wpv3Pc@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: linkBe 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).