public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "markus dot heichel at comsoft dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ada/34799] New: [Ada] Assertion fails when no component clause is given for generic record member Date: Tue, 15 Jan 2008 15:48:00 -0000 [thread overview] Message-ID: <bug-34799-12295@http.gcc.gnu.org/bugzilla/> (raw) In the example below gcc reports an assertion failure, when warnings are switched on. > gcc -c -gnatwa status.ads fails, while > gcc -c status.ads is working. The snapshot 4.3.0 20070921 is correctly warning 'no component clause given for "C" declared at line 12' while later snapshots (e.g. 4.3.0 20080111) fail. status.ads ================================================ package STATUS is generic type CUSTOM_T is private; package HANDLER is type STORAGE_T is record A : Boolean; B : Boolean; C : CUSTOM_T; end record; for STORAGE_T use record A at 0 range 0..0; B at 1 range 0..0; end record; end HANDLER; end STATUS; ================================================ -- Summary: [Ada] Assertion fails when no component clause is given for generic record member Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: ada AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: markus dot heichel at comsoft dot de GCC build triplet: i686-pc-linux GCC host triplet: i686-pc-linux GCC target triplet: i686-pc-linux http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34799
next reply other threads:[~2008-01-15 15:30 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-01-15 15:48 markus dot heichel at comsoft dot de [this message] 2008-02-24 9:12 ` [Bug ada/34799] " sam at gcc dot gnu dot org 2008-02-27 11:55 ` sam at gcc dot gnu dot org 2008-02-27 11:58 ` sam at gcc dot gnu dot 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-34799-12295@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).