https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78014
Jiang An changed:
What|Removed |Added
CC||de34 at live dot cn
--- Comment #9 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78014
--- Comment #8 from Sam James ---
FWIW, the Clang counterpart to this bug is
https://github.com/llvm/llvm-project/issues/41959.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78014
Dr. David Alan Gilbert changed:
What|Removed |Added
CC||dgilbert at redhat dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78014
Martin Sebor changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78014
Martin Sebor changed:
What|Removed |Added
CC||msebor at gcc dot gnu.org
--- Comment #5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78014
David Malcolm changed:
What|Removed |Added
CC||dmalcolm at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78014
--- Comment #3 from Tom Tromey ---
(In reply to jos...@codesourcery.com from comment #2)
> Likewise an expression where the user did "typedef size_t my_size_t;" and
> then used my_size_t. And what about expressions resulting from arithmetic
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78014
--- Comment #2 from joseph at codesourcery dot com ---
I think this is essentially the same as bug 77970 - making such warnings
smarter about the case of standard typedefs.
Of course an expression resulting from sizeof must be considered
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78014
Andrew Pinski changed:
What|Removed |Added
Keywords||diagnostic
Severity|normal
