public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dkm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/109472] [13 regression] False unread/unassigned warning for variable in local package
Date: Wed, 12 Apr 2023 14:31:36 +0000	[thread overview]
Message-ID: <bug-109472-4-O3BnGmBuqr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109472-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109472

--- Comment #2 from Marc Poulhiès <dkm at gcc dot gnu.org> ---
Regression starts from:

a8d17a88a52d2f773423adb55399d23ed5ea03c8 is the first bad commit
commit a8d17a88a52d2f773423adb55399d23ed5ea03c8
Author: Piotr Trojanek <trojanek@adacore.com>
Date:   Tue Jun 21 10:17:57 2022 +0200

    [Ada] Warn on unset objects in packages with no bodies

    Fix an inconsistency, where GNAT was warning about references to unset
    objects inside generic packages with no bodies but not inside ordinary
    packages with no bodies.

But the issue is probably not this particular change, that simply asks gnat to
warn on unreferenced entities. The error is most probably caused by the
Referenced(N) that returns False for 'X' entity.

  parent reply	other threads:[~2023-04-12 14:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-11 14:32 [Bug ada/109472] New: " simon at pushface dot org
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 [this message]
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-O3BnGmBuqr@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).