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: "aldyh at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 26 Jan 2018 16:26:13 +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
Aldy Hernandez <aldyh at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|aldyh at gcc dot gnu.org |unassigned at gcc dot gnu.org
--- Comment #22 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
FWIW, the C++ front-end would also need changes if we move
optimize_bit_field_compare to gimple, as the constexpr code
(cxx_eval_bit_field_ref()) can only handle optimized BIT_FIELD_REFs.
For instance, it cannot look into an array of bit-fields as it's expanding a
constructor, because it was expecting optimize_bit_field_compare() to have
flattened things out first. It would die on this:
(gdb) print debug_generic_stmt (whole)
{.u=0, .a={{.i=5, .k=0, .l=2}}, .b={{.j=6}}}