public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/101747] Two-argument version of attribute malloc does not perform overload resolution Date: Tue, 03 Aug 2021 20:27:44 +0000 [thread overview] Message-ID: <bug-101747-4-QAx6USWDcN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101747-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101747 Martin Sebor <msebor at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2021-08-03 CC| |msebor at gcc dot gnu.org Keywords| |rejects-valid Ever confirmed|0 |1 --- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> --- I suppose the return type of the allocator could be used for the disambiguation. The difficulty here is that the attribute handler is in code shared by the C and C++ front ends with no good way to call a language-specific routine to do overload resolution. Maybe the attribute should accept a string with the mangled name of the function in addition to a function name. IIRC, attribute copy has the same limitation.
next prev parent reply other threads:[~2021-08-03 20:27 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-03 11:49 [Bug c++/101747] New: " fweimer at redhat dot com 2021-08-03 20:27 ` msebor at gcc dot gnu.org [this message] 2022-11-17 10:23 ` [Bug c++/101747] " ro at gcc dot gnu.org 2022-12-28 19:57 ` pinskia at gcc dot gnu.org 2022-12-28 19:57 ` pinskia 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-101747-4-QAx6USWDcN@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).