[Bug middle-end/89230] Bogus uninited usage warning

2021-04-15 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89230 --- Comment #10 from CVS Commits --- The master branch has been updated by Martin Sebor : https://gcc.gnu.org/g:2dbbbe893f75f587c48111ab4c97cf5e74fb91bb commit r11-8202-g2dbbbe893f75f587c48111ab4c97cf5e74fb91bb Author: Martin Sebor Date:

[Bug middle-end/89230] Bogus uninited usage warning

2021-04-15 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89230 Martin Sebor changed: What|Removed |Added Known to fail||10.2.0, 7.3.0, 8.3.0, 9.2.0 Target

[Bug middle-end/89230] Bogus uninited usage warning

2019-11-11 Thread egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89230 --- Comment #8 from Eric Gallager --- (In reply to Eric Gallager from comment #7) > (In reply to Andrew Pinski from comment #3) > > (In reply to lavr from comment #2) > > > Okay, but "d" points to a clearly separate storage on stack within a

[Bug middle-end/89230] Bogus uninited usage warning

2019-05-12 Thread egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89230 --- Comment #7 from Eric Gallager --- (In reply to Andrew Pinski from comment #3) > (In reply to lavr from comment #2) > > Okay, but "d" points to a clearly separate storage on stack within a local > > frame. None of the pointers passed to

[Bug middle-end/89230] Bogus uninited usage warning

2019-02-12 Thread lavr at ncbi dot nlm.nih.gov
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89230 --- Comment #6 from lavr at ncbi dot nlm.nih.gov --- That said, any function call within the outer "if()" but before the inner "if()" would cause the warning, even if that call does not accept any pointers (and thus cannot alias with local "s").

[Bug middle-end/89230] Bogus uninited usage warning

2019-02-12 Thread lavr at ncbi dot nlm.nih.gov
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89230 --- Comment #5 from lavr at ncbi dot nlm.nih.gov --- Thank you Martin, for giving me the idea of where the problem might be stemming from! It does look like *printf() is not recognized by GCC as not modifying the local memory. But in your

[Bug middle-end/89230] Bogus uninited usage warning

2019-02-07 Thread msebor at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89230 Martin Sebor changed: What|Removed |Added Keywords||alias CC|

[Bug middle-end/89230] Bogus uninited usage warning

2019-02-07 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89230 Andrew Pinski changed: What|Removed |Added Status|UNCONFIRMED |WAITING Last reconfirmed|

[Bug middle-end/89230] Bogus uninited usage warning

2019-02-07 Thread lavr at ncbi dot nlm.nih.gov
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89230 --- Comment #2 from lavr at ncbi dot nlm.nih.gov --- Okay, but "d" points to a clearly separate storage on stack within a local frame. None of the pointers passed to (s)printf() relate to that area (either they are also clearly separate within

[Bug middle-end/89230] Bogus uninited usage warning

2019-02-06 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89230 --- Comment #1 from Andrew Pinski --- So what is happening here is GCC does not know the properties of sprintf/printf to know they can't modify memory therefor GCC cannot figure out d->D_fid[2] does not change from the first if statement to the