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.
