public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "saulius.grazulis at bti dot vu.lt" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/115666] Cloaking access to subprogram in a record allows storing anonymous access-to-subprogram value
Date: Thu, 27 Jun 2024 10:58:08 +0000 [thread overview]
Message-ID: <bug-115666-4-ynUsFZFhPG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-115666-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115666
--- Comment #4 from Saulius Gražulis <saulius.grazulis at bti dot vu.lt> ---
Hi, Eric,
thank you for updating the bug #115666 status!
I am bit puzzled by your comment "nobody should write this sort of
things". Could you please let me know in somewhat more detail what was
wrong with my bug report? I am relatively new to GCC/GNAT Bugzilla, so I
would like to avoid mistakes in the future :)
Cheers,
Saulius
On 2024-06-27 13:45, ebotcazou at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115666
>
> Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Ever confirmed|0 |1
> Status|UNCONFIRMED |NEW
> CC| |ebotcazou at gcc dot gnu.org
> Last reconfirmed| |2024-06-27
>
> --- Comment #2 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> Confirmed, but nobody should write this sort of things.
>
> --
> You are receiving this mail because:
> You reported the bug.
> You are on the CC list for the bug.
next prev parent reply other threads:[~2024-06-27 10:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 13:26 [Bug ada/115666] New: " saulius.grazulis at bti dot vu.lt
2024-06-26 13:29 ` [Bug ada/115666] " saulius.grazulis at bti dot vu.lt
2024-06-27 10:45 ` ebotcazou at gcc dot gnu.org
2024-06-27 10:52 ` saulius.grazulis at bti dot vu.lt
2024-06-27 10:58 ` saulius.grazulis at bti dot vu.lt [this message]
2024-06-27 10:58 ` ebotcazou at gcc dot gnu.org
2024-06-27 11:15 ` saulius.grazulis at bti dot vu.lt
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-115666-4-ynUsFZFhPG@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).