public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "simon at pushface dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ada/109472] New: [13 regression] False unread/unassigned warning for variable in local package Date: Tue, 11 Apr 2023 14:32:34 +0000 [thread overview] Message-ID: <bug-109472-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109472 Bug ID: 109472 Summary: [13 regression] False unread/unassigned warning for variable in local package Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: ada Assignee: unassigned at gcc dot gnu.org Reporter: simon at pushface dot org CC: dkm at gcc dot gnu.org Target Milestone: --- Created attachment 54830 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54830&action=edit Demonstrator The compiler warns that a variable in a local package is not assigned and not read, even though it is assigned and read in code outside the package. GNAT 13.0.1 20230409 (experimental) Copyright 1992-2023, Free Software Foundation, Inc. Compiling: test_wu.adb Source file time stamp: 2023-04-11 14:20:32 Compiled at: 2023-04-11 15:30:49 1. procedure Test_Wu is 2. 3. package P is 4. X : Integer; | >>> warning: variable "X" is never read and never assigned [-gnatwu] 5. end; 6. 7. Y : Integer; 8. 9. begin 10. P.X := 5; 11. Y := P.X; 12. end; 12 lines: No errors, 1 warning
next reply other threads:[~2023-04-11 14:32 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-11 14:32 simon at pushface dot org [this message] 2023-04-12 8:45 ` [Bug ada/109472] " ebotcazou at gcc dot gnu.org 2023-04-12 10:28 ` rguenth at gcc dot gnu.org 2023-04-12 14:31 ` dkm at gcc dot gnu.org 2023-04-26 6:58 ` [Bug ada/109472] [13/14 regression] False unread/unassigned warning for variable in local package since r13-1626-ga8d17a88a52d2f rguenth at gcc dot gnu.org 2023-07-27 9:25 ` rguenth at gcc dot gnu.org 2024-05-21 9:14 ` [Bug ada/109472] [13/14/15 " jakub 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-109472-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: 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).