public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "simon at pushface dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ada/99360] [12 regression] ICE in generalized iteration Date: Sat, 12 Feb 2022 17:17:07 +0000 [thread overview] Message-ID: <bug-99360-4-2sG1nFNxE4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99360-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99360 --- Comment #9 from simon at pushface dot org --- In gcc 12.0.1 of 20220128, we get $ gnatmake -c -u -f iteration.adb gcc -c iteration.adb a-stream.ads:82:04: error: construct not allowed in configurable run-time mode a-stream.ads:82:04: error: file s-putima.ads had semantic errors a-stream.ads:82:04: error: entity "System.Put_Images.Put_Image_Unknown" not available s-putima.ads:63:53: error: "Long_Long_Long_Unsigned" not declared in "Unsigned_Types" gnatmake: "iteration.adb" compilation error which means we no longer get the ICE. Instead, the compiler complains validly that the old RTS files provided don’t provide the interfaces that the compiler now needs. Similarly for GCC 11.2. So, I think this PR should be closed as fixed.
next prev parent reply other threads:[~2022-02-12 17:17 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-03 11:55 [Bug ada/99360] New: " simon at pushface dot org 2021-03-04 9:04 ` [Bug ada/99360] [11 regression] " ebotcazou at gcc dot gnu.org 2021-03-04 9:19 ` ebotcazou at gcc dot gnu.org 2021-03-04 9:27 ` ebotcazou at gcc dot gnu.org 2021-03-04 22:37 ` simon at pushface dot org 2021-03-04 22:58 ` ebotcazou at gcc dot gnu.org 2021-04-09 8:29 ` rguenth at gcc dot gnu.org 2021-04-21 9:19 ` [Bug ada/99360] [11/12 " cvs-commit at gcc dot gnu.org 2021-04-21 9:21 ` [Bug ada/99360] [12 " ebotcazou at gcc dot gnu.org 2021-04-27 11:40 ` jakub at gcc dot gnu.org 2021-07-28 7:06 ` rguenth at gcc dot gnu.org 2022-02-12 17:17 ` simon at pushface dot org [this message] 2022-02-12 17:41 ` charlet 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-99360-4-2sG1nFNxE4@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).