https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85734
--- Comment #6 from Sam James ---
Paul noted at
https://lists.gnu.org/archive/html/bug-gnulib/2023-05/msg00139.html that this
seems to have come back, but interestingly, this bug never got closed in the
first place.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85734
--- Comment #5 from prathamesh3492 at gcc dot gnu.org ---
Fixed on trunk.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85734
--- Comment #4 from prathamesh3492 at gcc dot gnu.org ---
Author: prathamesh3492
Date: Tue May 15 04:44:33 2018
New Revision: 260249
URL: https://gcc.gnu.org/viewcvs?rev=260249&root=gcc&view=rev
Log:
2018-05-15 Prathamesh Kulkarni
PR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85734
prathamesh3492 at gcc dot gnu.org changed:
What|Removed |Added
CC||prathamesh3492 at gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85734
--- Comment #2 from Jan Hubicka ---
There is function_always_visible_to_compiler_p which should disable this sort
of warning. So I suppose we want to test it prior warning about malloc
attribute?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85734
Richard Biener changed:
What|Removed |Added
Keywords||diagnostic
Status|UNCONFIRM
