public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "coopht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/48918] GNAT Bug Box with Assert_Failure with einfo.adb:2661
Date: Tue, 21 Feb 2012 08:12:00 -0000 [thread overview]
Message-ID: <bug-48918-4-M9BeiGjFDp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48918-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48918
Alexander Basov <coopht at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |coopht at gmail dot com
--- Comment #1 from Alexander Basov <coopht at gmail dot com> 2012-02-21 06:41:46 UTC ---
Confirmed on trunk:
gcc -c -gnat12 buffers.ads
+===========================GNAT BUG DETECTED==============================+
| 4.7.0 20120221 (experimental) (x86_64-unknown-linux-gnu) Assert_Failure
einfo.adb:2742|
| Error detected at buffers.ads:3:58 |
| 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 or gnatmake command that you entered. |
| Also include sources listed below in gnatchop format |
| (concatenated together with no headers between files). |
+==========================================================================+
gnat version:
/opt/gcc-trunk/bin/gnatmake -v
GNATMAKE 4.7.0 20120221 (experimental)
Copyright (C) 1995-2012, Free Software Foundation, Inc.
next prev parent reply other threads:[~2012-02-21 6:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-06 22:28 [Bug ada/48918] New: " anhvofrcaus at gmail dot com
2012-02-21 8:12 ` coopht at gmail dot com [this message]
2015-01-03 5:41 ` [Bug ada/48918] " aoliva at gcc dot gnu.org
2015-01-03 17:19 ` anhvofrcaus at gmail 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-48918-4-M9BeiGjFDp@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).