[Bug sanitizer/83219] [8 regression] c-c++-common/ubsan/unreachable-2.c fails starting with r255201

2017-12-01 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83219 Jakub Jelinek changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug sanitizer/83219] [8 regression] c-c++-common/ubsan/unreachable-2.c fails starting with r255201

2017-12-01 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83219 --- Comment #12 from Jakub Jelinek --- Author: jakub Date: Fri Dec 1 08:08:55 2017 New Revision: 255295 URL: https://gcc.gnu.org/viewcvs?rev=255295=gcc=rev Log: PR sanitizer/83219 * tree-cfg.c: Include asan.h.

[Bug sanitizer/83219] [8 regression] c-c++-common/ubsan/unreachable-2.c fails starting with r255201

2017-11-30 Thread rguenther at suse dot de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83219 --- Comment #11 from rguenther at suse dot de --- On Thu, 30 Nov 2017, jakub at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83219 > > --- Comment #9 from Jakub Jelinek --- > Created attachment 42751 > -->

[Bug sanitizer/83219] [8 regression] c-c++-common/ubsan/unreachable-2.c fails starting with r255201

2017-11-30 Thread andrey.y.guskov at intel dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83219 --- Comment #10 from Andrey Guskov --- Confirmed on Haswell and Silvermont.

[Bug sanitizer/83219] [8 regression] c-c++-common/ubsan/unreachable-2.c fails starting with r255201

2017-11-30 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83219 --- Comment #9 from Jakub Jelinek --- Created attachment 42751 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=42751=edit gcc8-pr83219.patch Untested fix.

[Bug sanitizer/83219] [8 regression] c-c++-common/ubsan/unreachable-2.c fails starting with r255201

2017-11-30 Thread rguenther at suse dot de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83219 --- Comment #8 from rguenther at suse dot de --- On Thu, 30 Nov 2017, jakub at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83219 > > --- Comment #6 from Jakub Jelinek --- > For the -fsanitize=unreachable, maybe just

[Bug sanitizer/83219] [8 regression] c-c++-common/ubsan/unreachable-2.c fails starting with r255201

2017-11-30 Thread rguenther at suse dot de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83219 --- Comment #7 from rguenther at suse dot de --- On Thu, 30 Nov 2017, jakub at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83219 > > --- Comment #5 from Jakub Jelinek --- > Because new __builtin_unreachable calls are

[Bug sanitizer/83219] [8 regression] c-c++-common/ubsan/unreachable-2.c fails starting with r255201

2017-11-30 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83219 --- Comment #6 from Jakub Jelinek --- For the -fsanitize=unreachable, maybe just gimple_seq_unreachable_p shouldn't return true ever if sanitize_flags_p (SANITIZE_UNREACHABLE).

[Bug sanitizer/83219] [8 regression] c-c++-common/ubsan/unreachable-2.c fails starting with r255201

2017-11-30 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83219 --- Comment #5 from Jakub Jelinek --- Because new __builtin_unreachable calls are added everywhere in the optimization pipeline. I'd rather disable the optimizations where we remove conditionals or switches that branch to __builtin_unreachable

[Bug sanitizer/83219] [8 regression] c-c++-common/ubsan/unreachable-2.c fails starting with r255201

2017-11-30 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83219 Richard Biener changed: What|Removed |Added CC||mpolacek at gcc dot gnu.org ---

[Bug sanitizer/83219] [8 regression] c-c++-common/ubsan/unreachable-2.c fails starting with r255201

2017-11-30 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83219 --- Comment #3 from Richard Biener --- pass_sanopt it seems. Quite late. So how is this supposed to work? The testcase is int e; int main (void) { return e ? 0 : (__builtin_unreachable (), 1); } and I bet that if we do int e; int main

[Bug sanitizer/83219] [8 regression] c-c++-common/ubsan/unreachable-2.c fails starting with r255201

2017-11-30 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83219 --- Comment #2 from Richard Biener --- Hum. Where do we "instrument" __builtin_unreachable () for UBSAN? EVRP is now more aggressive with recording ranges, where VRP does it only for SSA names used dominated by an edge EVRP does it always.

[Bug sanitizer/83219] [8 regression] c-c++-common/ubsan/unreachable-2.c fails starting with r255201

2017-11-30 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83219 Richard Biener changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last reconfirmed|