https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109835
--- Comment #6 from Eric Gallager ---
(In reply to Sam James from comment #5)
> FWIW, after doing more of this work, I've decided I don't really care that
> much about this one.
>
> I still think FP mismatches are often worse, but there's
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109835
--- Comment #5 from Sam James ---
FWIW, after doing more of this work, I've decided I don't really care that much
about this one.
I still think FP mismatches are often worse, but there's enough junk pointer
type mismatches that I'm not sure we
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109835
--- Comment #4 from Sam James ---
(In reply to Eric Gallager from comment #3)
> I thought that there was already a separate bug for this, but it turns out
> that I was thinking of bug 87379, which is for something different...
Good catch. I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109835
Eric Gallager changed:
What|Removed |Added
CC||egallager at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109835
--- Comment #2 from Sam James ---
Okay, fair point, I gave examples but not *motivating* examples.
I have some non-harmless examples:
1.
https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1e0e5c4d289004fa779c86da9319cf2bb18548b1
(a nasty
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109835
--- Comment #1 from Florian Weimer ---
Presumably the idea is to enable -Werror=incompatible-function-pointer-types
(in spirit) because it is more severe than -Wincompatible-pointer-types? I'm
not sure this is actually true.
Your first example
