[Bug c++/116090] New: [11 regression] Another -Wmaybe-uninitialized false positive with std::optional

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116090 Bug ID: 116090 Summary: [11 regression] Another -Wmaybe-uninitialized false positive with std::optional Product: gcc Version: 14.1.1 Status: UNCONFIRMED

[Bug c++/115616] New: Friend-injecting a template function causes an ICE if you inject after trying to instantiate that function

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115616 Bug ID: 115616 Summary: Friend-injecting a template function causes an ICE if you inject after trying to instantiate that function Product: gcc Version: 14.1.0 Status:

[Bug libstdc++/112832] New: [std::format] Broken non-SFINAE-friendly `set_debug_format()` for `const char *` formatter

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112832 Bug ID: 112832 Summary: [std::format] Broken non-SFINAE-friendly `set_debug_format()` for `const char *` formatter Product: gcc Version: 13.2.0 Status: UNCONFIRMED

[Bug c++/111771] Incorrect "is used uninitialized" warning, as if zero-initialization didn't propagate through user-provided default constructors

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111771 --- Comment #2 from Egor --- Before calling A's constructor, it will zero `x` anyway. I was also surprised when I learned this yesterday, but it's what the standard says. 1. `()` performs value-initialization on B:

[Bug c++/111771] New: Incorrect "is used uninitialized" warning, as if zero-initialization didn't propagate through user-provided default constructors

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111771 Bug ID: 111771 Summary: Incorrect "is used uninitialized" warning, as if zero-initialization didn't propagate through user-provided default constructors Product: gcc

[Bug c++/108335] New: New-expression doesn't perform mandatory copy elision when copy constructor is disabled with `requires`, in a template

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108335 Bug ID: 108335 Summary: New-expression doesn't perform mandatory copy elision when copy constructor is disabled with `requires`, in a template Product: gcc

[Bug c++/107111] GCC accepts invalid program involving function declaration with pack expansion

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107111 --- Comment #4 from Egor --- *** Bug 107113 has been marked as a duplicate of this bug. ***

[Bug c++/107113] In function parameter list, `...` expanding a pack is accepted after `()` of a parameter declarator, but not before

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107113 Egor changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug c++/107111] GCC accepts invalid program involving function declaration with pack expansion

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107111 Egor changed: What|Removed |Added CC||iamsupermouse at mail dot ru --- Comment #3

[Bug c++/107113] New: In function parameter list, `...` expanding a pack is accepted after `()` of a parameter declarator, but not before

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107113 Bug ID: 107113 Summary: In function parameter list, `...` expanding a pack is accepted after `()` of a parameter declarator, but not before Product: gcc

[Bug libstdc++/106676] [C++20] Automatic iterator_category detection misbehaves when `::reference` is an rvalue reference, refuses to accept a forward iterator

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106676 --- Comment #1 from Egor --- I was told this is a wording defect. The `cpp17-forward-iterator` exposition-only concept in https://eel.is/c++draft/iterator.traits only permits lvalue references.

[Bug libstdc++/106676] New: [C++20] Automatic iterator_category detection misbehaves when `::reference` is an rvalue reference, refuses to accept a forward iterator

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106676 Bug ID: 106676 Summary: [C++20] Automatic iterator_category detection misbehaves when `::reference` is an rvalue reference, refuses to accept a forward iterator Product:

[Bug c++/105967] New: Forming a pointer to ref-qualified member function using a function typedef ignores the qualifier

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105967 Bug ID: 105967 Summary: Forming a pointer to ref-qualified member function using a function typedef ignores the qualifier Product: gcc Version: 12.1.1 Status:

[Bug c++/53288] [C++11] Lifetime of temporary object backing pointer-to-member expression not extended

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53288 Egor changed: What|Removed |Added CC||iamsupermouse at mail dot ru --- Comment #4 from

[Bug libstdc++/103951] New: [C++2b] string_view range constructor, "exception specification ... depends on itself"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103951 Bug ID: 103951 Summary: [C++2b] string_view range constructor, "exception specification ... depends on itself" Product: gcc Version: unknown Status: UNCONFIRMED

[Bug c++/103811] New: [c++20] ICE when a lambda is used as a template argument of another lambda's function parameter

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103811 Bug ID: 103811 Summary: [c++20] ICE when a lambda is used as a template argument of another lambda's function parameter Product: gcc Version: unknown Status:

[Bug c++/101442] Destructor not called for a temporary object, if it's bound to a ref member of an object subject to NRVO

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101442 --- Comment #1 from Egor --- Example is provided below. It prints `A()` and nothing else. I expected it to also pring `~A()`. ``` #include struct A { A() {std::cout << "A()\n";} A(const A &) = delete; A =(const A &) = delete;

[Bug c++/101442] New: Destructor not called for a temporary object, if it

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101442 Bug ID: 101442 Summary: Destructor not called for a temporary object, if it Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3