diff options
| author | Stefan Schulze Frielinghaus <stefansf@linux.ibm.com> | 2020-05-05 19:44:19 +0200 |
|---|---|---|
| committer | Stefan Schulze Frielinghaus <stefansf@linux.ibm.com> | 2020-05-18 20:04:25 +0200 |
| commit | 2c832ffedf06ff614fc36c44ab6c892d84075e08 (patch) | |
| tree | 209b08caabf201f8890e8898bcf27575261a7f82 /gcc/fortran/arith.c | |
| parent | be464161b4ae128681958d94aa460531cf30e0a4 (diff) | |
| download | gcc-2c832ffedf06ff614fc36c44ab6c892d84075e08.zip gcc-2c832ffedf06ff614fc36c44ab6c892d84075e08.tar.gz gcc-2c832ffedf06ff614fc36c44ab6c892d84075e08.tar.bz2 | |
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.
Diffstat (limited to 'gcc/fortran/arith.c')
0 files changed, 0 insertions, 0 deletions