public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gcc at davidb dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ada/52120] New: [Ada] Compiler assertion in iterator Date: Sat, 04 Feb 2012 06:45:00 -0000 [thread overview] Message-ID: <bug-52120-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52120 Bug #: 52120 Summary: [Ada] Compiler assertion in iterator Classification: Unclassified Product: gcc Version: 4.6.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: ada AssignedTo: unassigned@gcc.gnu.org ReportedBy: gcc@davidb.org Created attachment 26570 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26570 bug sources in gnatchop format gcc-4.6 -c -gnat12 heap_sieve.adb +===========================GNAT BUG DETECTED==============================+ | 4.6.2 (x86_64-pc-linux-gnu) Assert_Failure sinfo.adb:1072 | | Error detected at heap_sieve.adb:83:30 | | Please submit a bug report; see http://gcc.gnu.org/bugs.html. | | Use a subject line meaningful to you and us to track the bug. | | Include the entire contents of this bug box in the report. | | Include the exact gcc-4.6 or gnatmake command that you entered. | | Also include sources listed below in gnatchop format | | (concatenated together with no headers between files). | +==========================================================================+ Code is attached. Seems to be provoked by the for Step of ... construct. The commented out code after it works as a workaround. apt-cache show gnat-4.6 Package: gnat-4.6 Version: 4.6.2-3 (Debian Testing, amd64)
next reply other threads:[~2012-02-04 6:45 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-04 6:45 gcc at davidb dot org [this message] 2012-02-12 23:11 ` [Bug ada/52120] " nicolas.boulenguez at free dot fr 2013-10-31 0:31 ` nicolas.boulenguez at free dot fr 2015-01-03 5:41 ` aoliva 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-52120-4@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).