[Bug c++/115229] inconsistent `error: possibly dangling reference to a temporary`

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115229 --- Comment #2 from Barnabás Pőcze --- So because `A::p` might point into the temporary of type `B` returned by `f()`, the warning is shown? If so, why don't I get a warning if `x` is not a reference? The same potential issue is possible in

[Bug c++/115229] New: inconsistent `error: possibly dangling reference to a temporary`

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115229 Bug ID: 115229 Summary: inconsistent `error: possibly dangling reference to a temporary` Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: normal

[Bug c++/115222] New: clang does not think libstdc++'s std::optional is nothrow destructible

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115222 Bug ID: 115222 Summary: clang does not think libstdc++'s std::optional is nothrow destructible Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: normal

[Bug c++/115219] [11/12/13/14/15 Regression] [c++17+] ICE on depdendent noexcept class operator delete

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115219 --- Comment #3 from Barnabás Pőcze --- That reduced test case compiles fine for me. On CE, too. Am I missing some compilation flags?

[Bug c++/115219] New: ICE on conditionally noexcept class operator delete

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115219 Bug ID: 115219 Summary: ICE on conditionally noexcept class operator delete Product: gcc Version: 14.1.1 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug c++/113835] New: compiling std::vector with const size in C++20 is slow

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113835 Bug ID: 113835 Summary: compiling std::vector with const size in C++20 is slow Product: gcc Version: 13.2.1 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug sanitizer/113053] New: local variable misaligned with AddressSanitizer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113053 Bug ID: 113053 Summary: local variable misaligned with AddressSanitizer Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3

[Bug libstdc++/112934] New: excessive code for std::map::erase(key)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112934 Bug ID: 112934 Summary: excessive code for std::map::erase(key) Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug c/80454] -Wmissing-braces wrongly warns about universal zero initializer {0}

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80454 Barnabás Pőcze changed: What|Removed |Added CC||pobrn at protonmail dot com ---

[Bug c++/108238] auto return type and some attributes don't get along

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108238 --- Comment #5 from Barnabás Pőcze --- Based on a suggestion from Jakub Jelínek, I have tried to modify `is_late_template_attribute()` instead, but it appears that function does not run in this case.

[Bug c++/107532] [13 Regression] -Werror=dangling-reference false positives in libcamera-0.0.1

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107532 --- Comment #17 from Barnabás Pőcze --- The simple test case with std::span still triggers the warning: https://gcc.godbolt.org/z/43cKxdqr3. I feel that without deeper code analysis such a warning will generate too many false positives and

[Bug tree-optimization/108802] New: missed inlining of call via pointer to member function

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108802 Bug ID: 108802 Summary: missed inlining of call via pointer to member function Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug c++/107532] [13 Regression] -Werror=dangling-reference false positives in libcamera-0.0.1

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107532 Barnabás Pőcze changed: What|Removed |Added CC||pobrn at protonmail dot com ---

[Bug c++/108238] returns_nonnull attribute with auto return type fails to compile

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108238 --- Comment #2 from Barnabás Pőcze --- Here is a change that I believe might address this. It seems to work but I have never done anything in gcc, so probably has shortcomings. The error points to the return expression, like this: asd2.cpp:

[Bug c++/108238] New: returns_nonnull attribute with auto return type fails to compile

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108238 Bug ID: 108238 Summary: returns_nonnull attribute with auto return type fails to compile Product: gcc Version: 12.2.0 Status: UNCONFIRMED Severity: normal

[Bug middle-end/104151] [10/11/12/13 Regression] x86: excessive code generated for 128-bit byteswap

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104151 Barnabás Pőcze changed: What|Removed |Added CC||pobrn at protonmail dot com ---

[Bug c++/105667] [C++20] lambas in template argument sometimes causes an ICE (seg fault)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105667 Barnabás Pőcze changed: What|Removed |Added CC||pobrn at protonmail dot com ---

[Bug sanitizer/95137] Sanitizers seem to be missing support for coroutines

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95137 Barnabás Pőcze changed: What|Removed |Added CC||pobrn at protonmail dot com ---