aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKewen Lin <linkw@linux.ibm.com>2023-07-17 03:44:59 -0500
committerKewen Lin <linkw@linux.ibm.com>2023-07-17 03:44:59 -0500
commit081c623ca88dc53abe34b5f5661e79fcde800cef (patch)
tree9d0b7d6b4f43a02a9a95c4b5aee37dcf28a27edc
parent3228e5c078ed2b505e4ad238b09c1817b38f9cfb (diff)
downloadgcc-081c623ca88dc53abe34b5f5661e79fcde800cef.zip
gcc-081c623ca88dc53abe34b5f5661e79fcde800cef.tar.gz
gcc-081c623ca88dc53abe34b5f5661e79fcde800cef.tar.bz2
vect: Initialize new_temp to avoid false positive warning [PR110652]
As PR110652 and its duplicate PRs show, there could be one build error error: 'new_temp' may be used uninitialized for some build configurations. It's a false positive warning (or error at -Werror), but in order to make the build succeed, this patch is to initialize the reported variable 'new_temp' as NULL_TREE. PR tree-optimization/110652 gcc/ChangeLog: * tree-vect-stmts.cc (vectorizable_load): Initialize new_temp as NULL_TREE.
-rw-r--r--gcc/tree-vect-stmts.cc3
1 files changed, 2 insertions, 1 deletions
diff --git a/gcc/tree-vect-stmts.cc b/gcc/tree-vect-stmts.cc
index c08d0ef..cb86d54 100644
--- a/gcc/tree-vect-stmts.cc
+++ b/gcc/tree-vect-stmts.cc
@@ -9297,7 +9297,8 @@ vectorizable_load (vec_info *vinfo,
class loop *containing_loop = gimple_bb (stmt_info->stmt)->loop_father;
bool nested_in_vect_loop = false;
tree elem_type;
- tree new_temp;
+ /* Avoid false positive uninitialized warning, see PR110652. */
+ tree new_temp = NULL_TREE;
machine_mode mode;
tree dummy;
tree dataref_ptr = NULL_TREE;