public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Giuliano Belinassi <giulianob@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc/devel/autopar_devel] tree-optimization: Fix use of uninitialized variables warnings [PR94952] Date: Sat, 22 Aug 2020 21:21:03 +0000 (GMT) [thread overview] Message-ID: <20200822212103.B6DC23851C16@sourceware.org> (raw) https://gcc.gnu.org/g:8700d3a8360e686c8d5ee441b1fdbd7eb7e90e05 commit 8700d3a8360e686c8d5ee441b1fdbd7eb7e90e05 Author: Stefan Schulze Frielinghaus <stefansf@linux.ibm.com> Date: Tue May 5 19:44:19 2020 +0200 tree-optimization: Fix use of uninitialized variables warnings [PR94952] While bootstrapping GCC on S/390 with --enable-checking=release several warnings about use of uninitialized variables bitpos, bitregion_start, and bitregion_end of function pass_store_merging::process_store are raised. According to PR94952 these seem to be false positives which are silenced by initialising the mentioned variables. Bootstrapped on S/390. Ok for master and releases/gcc-10 assuming that regtest succeeds (still running but I don't see a reason why it should fail)? gcc/ChangeLog: 2020-05-18 Stefan Schulze Frielinghaus <stefansf@linux.ibm.com> PR tree-optimization/94952 * gimple-ssa-store-merging.c (pass_store_merging::process_store): Initialize variables bitpos, bitregion_start, and bitregion_end in order to silence warnings about use of uninitialized variables. Diff: --- gcc/ChangeLog | 7 +++++++ gcc/gimple-ssa-store-merging.c | 4 ++-- 2 files changed, 9 insertions(+), 2 deletions(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 51b5b6c908d..0a1ff053ffa 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,10 @@ +2020-05-18 Stefan Schulze Frielinghaus <stefansf@linux.ibm.com> + + PR tree-optimization/94952 + * gimple-ssa-store-merging.c (pass_store_merging::process_store): + Initialize variables bitpos, bitregion_start, and bitregion_end in + order to silence warnings about use of uninitialized variables. + 2020-05-18 Carl Love <cel@us.ibm.com> PR target/94833 diff --git a/gcc/gimple-ssa-store-merging.c b/gcc/gimple-ssa-store-merging.c index 25753517cc6..c8e1877f540 100644 --- a/gcc/gimple-ssa-store-merging.c +++ b/gcc/gimple-ssa-store-merging.c @@ -4668,8 +4668,8 @@ pass_store_merging::process_store (gimple *stmt) { tree lhs = gimple_assign_lhs (stmt); tree rhs = gimple_assign_rhs1 (stmt); - poly_uint64 bitsize, bitpos; - poly_uint64 bitregion_start, bitregion_end; + poly_uint64 bitsize, bitpos = 0; + poly_uint64 bitregion_start = 0, bitregion_end = 0; tree base_addr = mem_valid_for_store_merging (lhs, &bitsize, &bitpos, &bitregion_start, &bitregion_end);
reply other threads:[~2020-08-22 21:21 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20200822212103.B6DC23851C16@sourceware.org \ --to=giulianob@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).