public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "stephen_leake@stephe-leake.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/99099] New: bogus error on generic formal derived tagged type
Date: Mon, 15 Feb 2021 00:49:25 +0000 [thread overview]
Message-ID: <bug-99099-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99099
Bug ID: 99099
Summary: bogus error on generic formal derived tagged type
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: ada
Assignee: unassigned at gcc dot gnu.org
Reporter: stephen_leake@stephe-leake.org
Target Milestone: ---
Created attachment 50182
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50182&action=edit
source file
The attached code compiles with GNAT Community 2019 and 2020, but fails with
gcc 10.2:
$ gprbuild -p -P work.gpr
Setup
[mkdir] object directory for project work
Compile
[Ada] wisi.ads
[Ada] test_gen_emacs.adb
gen_emacs_wisi_lr_parse.ads:3:52: missing ";"
gprbuild: *** compilation phase failed
next reply other threads:[~2021-02-15 0:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-15 0:49 stephen_leake@stephe-leake.org [this message]
2021-02-15 0:52 ` [Bug ada/99099] " stephen_leake@stephe-leake.org
2021-02-15 11:33 ` stephen_leake@stephe-leake.org
2023-05-11 16:35 ` 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-99099-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: 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).