public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ada/22419] New: Ada produces mis-match (non compatible) types in MODIFY_EXPR Date: Mon, 11 Jul 2005 23:41:00 -0000 [thread overview] Message-ID: <20050711234043.22419.pinskia@gcc.gnu.org> (raw) Another case: with C392014_2; package body C392014_0 is function Create return T'Class is begin return C392014_2.Create ; end Create; end C392014_0; package C392014_0 is type T (D : natural) is abstract tagged null record; function Create return T'Class; end C392014_0; with C392014_0; with C392014_1; package C392014_2 is type T is new C392014_1.T with record C2 : natural; end record; function Create return T'Class; end C392014_2; with C392014_0; package C392014_1 is type T is new C392014_0.T with record C1 : natural; end record; end C392014_1; Again see PR 22368 for the patch which I used to find this. c392014_2.ads: In function 'C392014_0.Create': c392014_2.ads:9: error: statement types mismatch D.865 = D.866; struct c392014_0__tD.395 * struct c392014_2__tD.827 * -- Summary: Ada produces mis-match (non compatible) types in MODIFY_EXPR Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: ada AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: pinskia at gcc dot gnu dot org CC: bosch at gcc dot gnu dot org,gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22419
next reply other threads:[~2005-07-11 23:40 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-07-11 23:41 pinskia at gcc dot gnu dot org [this message] 2005-07-11 23:50 ` [Bug ada/22419] " pinskia at gcc dot gnu dot org 2005-09-06 8:34 ` ebotcazou 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=20050711234043.22419.pinskia@gcc.gnu.org \ --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).