public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rkraesig at mozilla dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/114812] Arguments of array type decay to pointer type too eagerly when used as arguments to ref- or ptr-to-function
Date: Mon, 22 Apr 2024 20:12:27 +0000 [thread overview]
Message-ID: <bug-114812-4-wPQe2zqVcn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114812-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114812
--- Comment #2 from Raymond Kraesig <rkraesig at mozilla dot com> ---
(In reply to Andrew Pinski from comment #1)
> Maybe a dup of one of the bugs linked from PR 24666.
It's none of the open bugs, as far as I can tell. Since it still happens on
trunk, I assume it's none of the closed bugs, either... although bug 41426 is
suspiciously similar.
prev parent reply other threads:[~2024-04-22 20:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 19:53 [Bug c++/114812] New: " rkraesig at mozilla dot com
2024-04-22 19:57 ` [Bug c++/114812] " pinskia at gcc dot gnu.org
2024-04-22 20:12 ` rkraesig at mozilla dot com [this message]
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-114812-4-wPQe2zqVcn@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).