This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug sanitizer/81601] [7/8 Regression] incorrect Warray-bounds warning with -fsanitize
- From: "ppalka at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sun, 30 Jul 2017 16:22:12 +0000
- Subject: [Bug sanitizer/81601] [7/8 Regression] incorrect Warray-bounds warning with -fsanitize
- Auto-submitted: auto-generated
- References: <bug-81601-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81601
--- Comment #6 from Patrick Palka <ppalka at gcc dot gnu.org> ---
(In reply to Patrick Palka from comment #5)
> So what's the right way to fix this? To move optimize_bit_field_compare()
> from fold_binary to match.pd so that the conditions on
... so that conditions on tp->chrono_type get consistently transformed into
BIT_FIELD_REFs, or to remove optimize_bit_field_compare() altogether? It seems
like a rather low-level optimization to be done in GENERIC/GIMPLE.