[Bug c++/119923] New: `-pedantic-errors` should imply `-fno-ms-extensions` on MinGW

Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: iamsupermouse at mail dot ru Target Milestone: --- GCC on Windows has a relatively little-known flag `-fno-ms-extensions`, which disables some problematic MSVC-like extensions, which

[Bug libstdc++/118699] [MinGW] std::filesystem::copy doesn't work when the second argument is a directory and the first one is a file

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118699 --- Comment #2 from Egor --- It says 14.2.0. So this is fixed in trunk, I assume... COLLECT_GCC=Z:\mingw64\bin\g++.exe COLLECT_LTO_WRAPPER=Z:/home/holyblackcat/.quasi-msys2/mingw64/root/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/14.2.0/l

[Bug libstdc++/118699] New: [MinGW] std::filesystem::copy doesn't work when the second argument is a directory and the first one is a file

rsion: 14.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: iamsupermouse at mail dot ru Target Milestone: --- The bug only happens on MinGW. This code: #in

[Bug c++/117106] New: ICE when a "deducing this" function with noexcept specification is used before the class is complete

Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: iamsupermouse at mail dot ru Target Milestone: --- The following code causes an internal compiler error in GCC 14 and trunk: https://gcc.g

[Bug c++/116289] [13 regression] Can't apply decltype to comparison operators created by spaceship operator for local classes

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116289 --- Comment #3 from Egor --- (In reply to Patrick Palka from comment #2) > r14-4140 ... doesn't seem suitable for backporting Fair enough. What's the procedure now, should I set status=resolved?

[Bug c++/116289] New: [13.3 regression] Can't apply decltype to comparison operators created by spaceship operator for local classes

rsion: 13.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: iamsupermouse at mail dot ru Target Milestone: --- This bug only affects 13.3. Works fine in 13.2 and in 14.x. H

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

Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: iamsupermouse at mail dot ru Target Milestone: --- I'm not sure if it's an exact duplicate, since there are many bugs about -Wmaybe-uninitialized false posit

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

: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: iamsupermouse at mail dot ru Target Milestone: --- The following causes an internal compiler error in GCC 14 and trunk: https

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

Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: iamsupermouse at mail dot ru Target Milestone: --- GCC doesn't seem to implement `{:?}` debug format for strings yet. Yet for some reason

[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: http://eel.is/c++draft/dcl.d

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

Product: gcc Version: 13.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: iamsupermouse at mail dot ru Target Milestone: --- Here's the code. GCC with `-

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

: gcc Version: 12.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: iamsupermouse at mail dot ru Target Milestone: --- This doesn't compile, but it should:

[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

: 12.1.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: iamsupermouse at mail dot ru Target Milestone: --- GCC rejects this code: template struct A

[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

: gcc Version: 12.1.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: iamsupermouse at mail dot ru Target Milestone: --- Since C++20, `std::iterator_traits

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

: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: iamsupermouse at mail dot ru Target Milestone: --- Consider following code: #include struct A {}; using F = void

[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"

NCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: iamsupermouse at mail dot ru Target Milestone: --- Following code compiles with -std=c++20 and earlier, but fails with -std=c++2b, in both GCC

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

tatus: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: iamsupermouse at mail dot ru Target Milestone: --- Following code causes an ICE (segfault): template struct A {}; int main()

[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 &operator=(const A &) = del

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

Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: iamsupermouse at mail dot ru Target Milestone: ---

[Bug libstdc++/91786] New: Clang 8.0.1 can't compile the header on Windows

y: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: iamsupermouse at mail dot ru Target Milestone: --- On Windows, Clang 8.0.1 refuses to compile the header with following errors: > In file included from ...\mingw64\include\c++\9.2.0\fi

[Bug c++/81099] New: A single `decltype(this)` at top level triggers 2 identical error messages

: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: iamsupermouse at mail dot ru Target Milestone: --- If `decltype(this)` is used at top level, it triggers *two* identical error messages. For example: using T = decltype

[Bug c++/80896] New: [[nodiscard]] is ignored for functions returning references

Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: iamsupermouse at mail dot ru Target Milestone: --- Following produces no warnings: int x = 42; [[nodiscard]] int &func() {return x;} int main() {func();} But removing

[Bug c++/64531] `casting between pointer-to-function and pointer-to-object` is still a warning instead of error with `-pedantic -pedantic-errors`

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64531 Egor changed: What|Removed |Added Severity|minor |normal

[Bug c++/64531] New: `casting between pointer-to-function and pointer-to-object` is still a warning instead of error with `-pedantic -pedantic-errors`

Version: 4.8.1 Status: UNCONFIRMED Severity: minor Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: iamsupermouse at mail dot ru `-pedantic` causes g++ to emit a warning `ISO C++ forbids casting between