This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/87953] asan: stack-buffer-overflow in vectorizable_reduction
- From: "rguenth at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 09 Nov 2018 11:06:37 +0000
- Subject: [Bug c/87953] asan: stack-buffer-overflow in vectorizable_reduction
- Auto-submitted: auto-generated
- References: <bug-87953-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87953
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2018-11-09
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
valgrind reports
==21312== Conditional jump or move depends on uninitialised value(s)
==21312== at 0x14BB78D: vectorizable_condition(_stmt_vec_info*,
gimple_stmt_iterator*, _stmt_vec_info**, tree_node*, int, _slp_tree*,
vec<stmt_info_for_cost, va_heap, vl_ptr>*) (tree-vect-stmts.c:8718)
==21312== by 0x14DCDC0: vectorizable_reduction(_stmt_vec_info*,
gimple_stmt_iterator*, _stmt_vec_info**, _slp_tree*, _slp_instance*,
vec<stmt_info_for_cost, va_heap, vl_ptr>*) (tree-vect-loop.c:6531)
so that's probably the very same thing. reduc_index is -1 here.
I have a fix.