[Bug middle-end/99797] accessing uninitialized automatic variables

2021-04-20 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99797 Martin Sebor changed: What|Removed |Added Resolution|--- |DUPLICATE CC|

[Bug middle-end/99797] accessing uninitialized automatic variables

2021-04-19 Thread muecker at gwdg dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99797 --- Comment #11 from Martin Uecker --- (In reply to Ivan Sorokin from comment #10) ... > > is a bug if this choice is unreasonable and does not serve its users well. > > Do you have some specific proposal in mind? > > Currently a user has

[Bug middle-end/99797] accessing uninitialized automatic variables

2021-04-19 Thread vanyacpp at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99797 Ivan Sorokin changed: What|Removed |Added CC||vanyacpp at gmail dot com --- Comment

[Bug middle-end/99797] accessing uninitialized automatic variables

2021-04-18 Thread muecker at gwdg dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99797 --- Comment #9 from Martin Uecker --- The behavior of GCC is dangerous as the example in comment #1 show. You can not reason at all about the generated code. It is not just that the uninitialized value causes some random choice but it creates

[Bug middle-end/99797] accessing uninitialized automatic variables

2021-04-18 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99797 Andrew Pinski changed: What|Removed |Added Component|c |middle-end --- Comment #8 from Andrew