[Bug tree-optimization/108379] -Wmaybe-uninitialized false positive on conditional use

[sam at gentoo dot org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108379

Sam James  changed:

   What|Removed |Added

 CC||eggert at cs dot ucla.edu

--- Comment #4 from Sam James  ---
tee -P is now in coreutils git. Paul's applied
https://git.savannah.gnu.org/cgit/coreutils.git/commit/?id=0789451237b90324a5d1f5c1b9fbaa5099f4c072
as a workaround to avoid this warning.

[Bug tree-optimization/108379] -Wmaybe-uninitialized false positive on conditional use

[pinskia at gcc dot gnu.org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108379

Andrew Pinski  changed:

   What|Removed |Added

   Keywords||diagnostic

--- Comment #3 from Andrew Pinski  ---
I suspect since pipe_check is global is causing the unintialized warning
conditional checks to be thrown off because I suspect GCC thinks it can be
modified between the 3 checks of pipe_check when out_pollable is used.

So if you did a local copy of pipe_check to cache it inside tee_files and use
that, the warning will go away.

[Bug tree-optimization/108379] -Wmaybe-uninitialized false positive on conditional use

[sam at gentoo dot org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108379

--- Comment #2 from Sam James  ---
Minimum command needed to reproduce:
```
$ gcc-13 -Werror -Wuninitialized -O2 -c tee.i
src/tee.c: In function 'tee_files':
src/tee.c:272:25: error: 'out_pollable' may be used uninitialized
[-Werror=maybe-uninitialized]
src/tee.c:238:8: note: 'out_pollable' was declared here
cc1: all warnings being treated as errors
```

[Bug tree-optimization/108379] -Wmaybe-uninitialized false positive on conditional use

[sam at gentoo dot org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108379

--- Comment #1 from Sam James  ---
Created attachment 54252
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54252=edit
coreutils-tee.patch