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/56474] [4.8 regression] bogus Storage_Error raised for record containing empty zero-based array
Date: Thu, 28 Feb 2013 11:02:00 -0000 [thread overview]
Message-ID: <bug-56474-4-rRIfzvGNH1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56474-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56474
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2013-02-28
CC| |ebotcazou at gcc dot
| |gnu.org
Target Milestone|--- |4.8.0
Summary|GNAT computes size of the |[4.8 regression] bogus
|object to be allocated |Storage_Error raised for
|incorrectly |record containing empty
| |zero-based array
Ever Confirmed|0 |1
Severity|critical |normal
--- Comment #1 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2013-02-28 11:01:37 UTC ---
Strange, we would rather lose warnings than issue bogus ones here.
In any case, the workaround is easy: use 1-based arrays instead.
next prev parent reply other threads:[~2013-02-28 11:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 17:41 [Bug ada/56474] New: GNAT computes size of the object to be allocated incorrectly pavel at zhukoff dot net
2013-02-28 11:02 ` ebotcazou at gcc dot gnu.org [this message]
2013-02-28 11:04 ` [Bug ada/56474] [4.8 regression] bogus Storage_Error raised for record containing empty zero-based array ebotcazou at gcc dot gnu.org
2013-03-01 11:28 ` rguenth at gcc dot gnu.org
2013-03-01 14:26 ` ebotcazou at gcc dot gnu.org
2013-03-01 14:33 ` [Bug middle-end/56474] " ebotcazou at gcc dot gnu.org
2013-03-04 9:53 ` rguenth at gcc dot gnu.org
2013-03-04 11:29 ` ebotcazou at gcc dot gnu.org
2013-03-04 15:12 ` rguenther at suse dot de
2013-03-04 15:39 ` ebotcazou at gcc dot gnu.org
2013-03-04 15:45 ` rguenther at suse dot de
2013-03-04 15:51 ` jakub at gcc dot gnu.org
2013-03-04 16:19 ` ebotcazou at gcc dot gnu.org
2013-03-05 9:05 ` rguenther at suse dot de
2013-03-06 17:21 ` ebotcazou at gcc dot gnu.org
2013-03-07 11:37 ` jakub at gcc dot gnu.org
2013-03-22 14:42 ` [Bug middle-end/56474] [4.8/4.9 " jakub at gcc dot gnu.org
2013-05-06 9:34 ` ebotcazou at gcc dot gnu.org
2013-05-07 7:50 ` [Bug ada/56474] " ebotcazou at gcc dot gnu.org
2013-05-07 8:07 ` ebotcazou at gcc dot gnu.org
2013-05-07 8:07 ` ebotcazou at gcc dot gnu.org
2013-05-07 8:08 ` 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-56474-4-rRIfzvGNH1@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).