[Bug c/110425] New: Docbug: missing name for builtin function (__builtin_alloca_with_align_and_max?)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110425 Bug ID: 110425 Summary: Docbug: missing name for builtin function (__builtin_alloca_with_align_and_max?) Product: gcc Version: 13.1.0 Status: UNCONFIRMED Sever

[Bug tree-optimization/102329] pointer "maybe uninitialized" right after assignment

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

[Bug c/102381] New: unexpected -Wmaybe-uninitialized

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102381 Bug ID: 102381 Summary: unexpected -Wmaybe-uninitialized Product: gcc Version: 7.5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c As

[Bug tree-optimization/102329] pointer "maybe uninitialized" right after assignment

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

[Bug c/102329] New: pointer "maybe uninitialized" right after assignment

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102329 Bug ID: 102329 Summary: pointer "maybe uninitialized" right after assignment Product: gcc Version: 11.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Comp

[Bug c/102291] New: dubious overflow warning

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102291 Bug ID: 102291 Summary: dubious overflow warning Product: gcc Version: 11.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: