https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111531
Bug ID: 111531
Summary: Bound member function (-Wno-pmf-conversions) with
multiple inheritance
Product: gcc
Version: 13.2.0
Status: UNCONFIRMED
Severity: norma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111531
--- Comment #3 from Paul Haile ---
Fair enough definitely could be intentional. However, In this example
renaming
typedef void (*b_fptr)(B *);
to
typedef void (*b_fptr)(A *);
gets rid of the error.
It seems restricting the binding such tha
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111531
--- Comment #4 from Paul Haile ---
The only time I could imagine allowing type mismatch would be in allowing the
function pointer to allow void * in type erased contexts.
e.g.
typedef void (*b_fptr)(void *);
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115693
Bug ID: 115693
Summary: 8 std::byte std::array comparison potential missed
optimization
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115693
--- Comment #4 from Paulous Haile ---
Maybe not necessary, just wanted to add a case for the default operator==. I
have noticed it also doesn't seem to coalesce adjacent cmps, which I assume is
part of the same issue.
#include
struct Point
{
