public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/101747] New: Two-argument version of attribute malloc does not perform overload resolution
Date: Tue, 03 Aug 2021 11:49:38 +0000	[thread overview]
Message-ID: <bug-101747-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 101747
           Summary: Two-argument version of attribute malloc does not
                    perform overload resolution
           Product: gcc
           Version: 11.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: fweimer at redhat dot com
  Target Milestone: ---

This:

struct T1;
struct T2;

void close(T1*);
void close(T2*);

T1* open(const char *) __attribute__ ((__malloc__ (close, 1)));

results in:

t.cc:7:62: error: ‘malloc’ attribute argument 1 is ambiguous
    7 | T1* open(const char *) __attribute__ ((__malloc__ (close, 1)));
      |                                                              ^
t.cc:7:62: note: use a cast to the expected type to disambiguate

This can be observed when building RawTherapee with glibc 2.34:
https://github.com/Beep6581/RawTherapee/issues/6324

Performing overload resolution in this context seems useful, given that the
exact type of the argument should be known at this point (the return type of
the function).

I'm not sure if should add the cast to the glibc sources to work around this.

             reply	other threads:[~2021-08-03 11:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-03 11:49 fweimer at redhat dot com [this message]
2021-08-03 20:27 ` [Bug c++/101747] " msebor at gcc dot gnu.org
2022-11-17 10:23 ` 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@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).