https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91707
Jeffrey A. Law changed:
What|Removed |Added
Priority|P3 |P2
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91707
--- Comment #6 from Martin Sebor ---
The nowarning idea in comment #5 is close to what I've been moving toward with
the new __builtin_warning intrinsic. Calls to it can be injected into the IL
by any pass, even the front-ends or user-defined cod
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91707
--- Comment #5 from Jakub Jelinek ---
Or mark the jump threading copies of stmts for sanitization (which start with
the __builtin___{asan,ubsan}_* calls) as nowarning.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91707
Jakub Jelinek changed:
What|Removed |Added
CC||law at gcc dot gnu.org
--- Comment #4 fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91707
--- Comment #3 from Jakub Jelinek ---
First of all, we shouldn't create such weirdo arrays, so I think we want
something like:
--- gcc/tree-ssa-ccp.c.jj 2019-09-20 12:25:26.809718354 +0200
+++ gcc/tree-ssa-ccp.c 2019-09-23 19:38:03.5307228
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91707
Martin Sebor changed:
What|Removed |Added
Blocks||88443
--- Comment #2 from Martin Sebor -
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91707
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
