[Bug middle-end/93644] [10/11/12 Regression] spurious -Wreturn-local-addr with PHI of PHI

2022-04-21 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93644

Richard Biener  changed:

   What|Removed |Added

   Target Milestone|11.3|11.4

--- Comment #21 from Richard Biener  ---
GCC 11.3 is being released, retargeting bugs to GCC 11.4.

[Bug middle-end/93644] [10/11/12 Regression] spurious -Wreturn-local-addr with PHI of PHI

2022-03-09 Thread grgoffe at yahoo dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93644

George R. Goffe  changed:

   What|Removed |Added

 CC||grgoffe at yahoo dot com

--- Comment #20 from George R. Goffe  ---
Hi,

I'm seeing this message from the "current" findutils.

What is the solution?

Best regards,

George...

[Bug middle-end/93644] [10/11/12 Regression] spurious -Wreturn-local-addr with PHI of PHI

2021-10-06 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93644

--- Comment #19 from Martin Sebor  ---
GCC 12 has changed to point the warning at the closing curly as suggested in
pr90735 so its output now looks like this:

pr93644.c: In function ‘careadlinkat’:
pr93644.c:30:1: warning: function may return address of local variable
[-Wreturn-local-addr]
   30 | }
  | ^
pr93644.c:6:8: note: declared here
6 |   char stack_buf[1024];
  |^

With that change the warning can also be suppressed by #pragma GCC diagnostic
placed before the closing curly.

GCC 12 also has separated the uninitialized predicate analyzer into a
standalone module but no warning except -Wmaybe-uninitialized makes use of it
yet.  This bug might be an opportunity to try it out.

[Bug middle-end/93644] [10/11/12 Regression] spurious -Wreturn-local-addr with PHI of PHI

2021-10-05 Thread egallager at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93644

--- Comment #18 from Eric Gallager  ---
This affects musl's getcwd implementation, btw:
https://git.musl-libc.org/cgit/musl/tree/src/unistd/getcwd.c?id=v1.2.2

[Bug middle-end/93644] [10/11/12 Regression] spurious -Wreturn-local-addr with PHI of PHI

2021-07-28 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93644

Richard Biener  changed:

   What|Removed |Added

   Target Milestone|11.2|11.3

--- Comment #17 from Richard Biener  ---
GCC 11.2 is being released, retargeting bugs to GCC 11.3

[Bug middle-end/93644] [10/11/12 Regression] spurious -Wreturn-local-addr with PHI of PHI

2021-05-04 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93644

Richard Biener  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED

[Bug middle-end/93644] [10/11/12 Regression] spurious -Wreturn-local-addr with PHI of PHI

2021-05-03 Thread jochen447 at concept dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93644

Jochen Roemmler  changed:

   What|Removed |Added

 CC||jochen447 at concept dot de

--- Comment #16 from Jochen Roemmler  ---
Created attachment 50739
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50739&action=edit
another minimal example to demonstrate the false alarm

This is another instance of the test case. A senseless, yet perfectly valid
piece of C code. It creates the false positive warning if compiled like this:

gcc -Wreturn-local-addr -O1 -fisolate-erroneous-paths-dereference -c
pr93644_2.c

pr93644_2.c: In function ‘buildVname’:
pr93644_2.c:28:12: warning: function may return address of local variable
[-Wreturn-local-addr]
   28 | return vname;
  |^
pr93644_2.c:18:17: note: declared here
   18 | charbuf[256];
  | ^~~


I'm using gcc version 11.1.1 20210428 (Red Hat 11.1.1-1) (GCC) 
However, I can silence the warning using

# pragma GCC diagnostic ignored "-Wreturn-local-addr"

[Bug middle-end/93644] [10/11/12 Regression] spurious -Wreturn-local-addr with PHI of PHI

2021-04-27 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93644

Jakub Jelinek  changed:

   What|Removed |Added

   Target Milestone|11.0|11.2

--- Comment #15 from Jakub Jelinek  ---
GCC 11.1 has been released, retargeting bugs to GCC 11.2.