https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70514
--- Comment #6 from Manuel López-Ibáñez ---
(In reply to Chris Warrick from comment #5)
> Thanks for debugging my code, and sorry for wasting time.
No problem. It is a pity that GCC static analysis capabilities are not powerful
enough to catch t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70514
--- Comment #5 from Chris Warrick ---
Thanks for debugging my code, and sorry for wasting time.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70514
Manuel López-Ibáñez changed:
What|Removed |Added
CC||manu at gcc dot gnu.org
--- Commen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70514
--- Comment #3 from Chris Warrick ---
Well, that is a typo. But would writing past the limits really have such
unusual effects? And why does clang++ not crash?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70514
Martin Sebor changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70514
--- Comment #1 from Andrew Pinski ---
This works for me on aarch64-linux-gnu with the trunk as of two days ago.
