public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "meudecc at itcarlow dot ie" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ada/35050] New: renames entities not in symbol table Date: Fri, 01 Feb 2008 12:17:00 -0000 [thread overview] Message-ID: <bug-35050-9333@http.gcc.gnu.org/bugzilla/> (raw) The example below illustrate that the .ali files do not always contain renamed subprograms references: >>> --pb_renaming.ads package pb_renaming is function Plus(X, Y: Integer) return Integer; function My_plus(X, Y: Integer) return Integer renames Plus; function Add(X, Y: Integer) return Integer renames "+"; A : Integer; end pb_renaming; >>> --pb_renaming.adb package body pb_renaming is function Plus(X, Y: Integer) return Integer is begin return X+Y; end Plus; begin --below, Add is properly cross-referenced by gnatxref in gnat v3.4.1 but not in gnat v4.1.3 --below, My_plus is never properly cross-referenced according to gnatxref output A := Add(4, 6) + My_plus(4, 6); end pb_renaming; >> Gnatxref output extract: My_plus function Decl: pb_renaming.ads 3:12 Reference entry is missing for My_plus regards, chris -- Summary: renames entities not in symbol table Product: gcc Version: 4.1.3 Status: UNCONFIRMED Severity: normal Priority: P3 Component: ada AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: meudecc at itcarlow dot ie http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35050
next reply other threads:[~2008-02-01 12:17 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-02-01 12:17 meudecc at itcarlow dot ie [this message] 2008-02-25 23:38 ` [Bug ada/35050] " sam at gcc dot gnu dot org 2008-02-29 15:51 ` [Bug ada/35050] [4.x regression] " tero dot koskinen at iki dot fi 2008-02-29 15:52 ` tero dot koskinen at iki dot fi 2008-02-29 16:11 ` sam at gcc dot gnu dot org 2008-03-27 22:22 ` [Bug ada/35050] [4.1/4.2/4.3/4.4 " rguenth at gcc dot gnu dot org 2008-04-14 9:40 ` sam at gcc dot gnu dot org 2008-04-14 9:42 ` 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-35050-9333@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).