https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102329
Florian Weimer changed:
What|Removed |Added
See Also||https://sourceware.org/bugz
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102329
--- Comment #6 from Martin Sebor ---
In general a program can add an attribute to a system function by redeclaring
it with it. This of course needs to be done conditionally on the GCC version
that supports the attribute. This in turn can be te
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102329
--- Comment #5 from Hugo van der Sanden ---
(In reply to Martin Sebor from comment #4)
> For functions like pthread_getspecific() and pthread_setspecific() that do
> not access the object GCC provides attribute access none to suppress the
> warn
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102329
--- Comment #4 from Martin Sebor ---
The text of the warning should be adjusted to make it clear that it's the
object the pointer points to that may be used uninitialized by the function.
For functions like pthread_getspecific() and pthread_set
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102329
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102329
--- Comment #2 from Hugo van der Sanden ---
I guess this is justified by the second paragraph of the -Wmaybe-uninitialized
docs: "In addition, passing a pointer (or in C++, a reference) to an
uninitialized object to a const-qualified function ar
