[Bug c++/88323] implement C++20 language features.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88323 Romain Geissler changed: What|Removed |Added CC||romain.geissler at amadeus dot com

[Bug libstdc++/114394] New: std::bind uses std::result_of which is deprecated

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114394 Bug ID: 114394 Summary: std::bind uses std::result_of which is deprecated Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug c++/114383] New: Wrong std::enable_if mangling ?

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114383 Bug ID: 114383 Summary: Wrong std::enable_if mangling ? Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++

[Bug sanitizer/111057] [11/12/13 only] build error: libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cpp:180:10: fatal error: crypt.h: No such file or directory

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111057 Romain Geissler changed: What|Removed |Added CC||romain.geissler at amadeus dot com

[Bug libstdc++/105562] [12 Regression] std::function::_M_invoker may be used uninitialized in std::regex move with -fno-strict-aliasing

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105562 --- Comment #28 from Romain Geissler --- Ok it's clear. I haven't really played yet with sanitizers, I didn't know it had these well known "issue" with creating more middle end false positive warnings (I am used to them in LTO mode). So I will

[Bug libstdc++/105562] [12 Regression] std::function::_M_invoker may be used uninitialized in std::regex move with -fno-strict-aliasing

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105562 --- Comment #25 from Romain Geissler --- So it means we should rather go for "silencing" workaround from comment #19 ?

[Bug libstdc++/105562] [12 Regression] std::function::_M_invoker may be used uninitialized in std::regex move with -fno-strict-aliasing

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105562 Romain Geissler changed: What|Removed |Added CC||romain.geissler at amadeus dot com

[Bug tree-optimization/106238] [12/13/14 regression] Inline optimization causes dangling pointer warning on "include/c++/12.1.0/bits/stl_tree.h"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106238 --- Comment #10 from Romain Geissler --- Hi, It seems the reproducers from comment #1 and #5 don't happen anymore with gcc 13 or trunk. So it seems fixed. Cheers, Romain

[Bug c/107954] Support -std=c23/gnu23 as aliases of -std=c2x/gnu2x

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107954 --- Comment #4 from Romain Geissler --- In the latest agenda published (https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3156.pdf) it seems that now the next C revision has been delayed a bit. At this point, is it known already if it will be

[Bug libstdc++/110133] New: System error message should ideally use strerror_r over strerror

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110133 Bug ID: 110133 Summary: System error message should ideally use strerror_r over strerror Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal

[Bug c++/109918] New: Unexpected -Woverloaded-virtual with virtual conversion operators

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109918 Bug ID: 109918 Summary: Unexpected -Woverloaded-virtual with virtual conversion operators Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal

[Bug libstdc++/108969] [13/14 Regression] Initializing iostreams in the library needs a GLIBCXX_3.4.31 versioned symbol

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108969 --- Comment #31 from Romain Geissler --- Ok thanks for confirming. I was about to ask for a deployment one of our gcc-based toolchain in production containing the current gcc 13.1.1, I will wait a bit that this patch lands in the gcc 13 branch

[Bug libstdc++/108969] [13/14 Regression] Initializing iostreams in the library needs a GLIBCXX_3.4.31 versioned symbol

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108969 --- Comment #29 from Romain Geissler --- Typo: If yes, given that you also maintain the gcc package in fedora 38 (https://src.fedoraproject.org/rpms/gcc/commits/f38), does it mean that something built in some future up to date Fedora 38 won't

[Bug libstdc++/108969] [13/14 Regression] Initializing iostreams in the library needs a GLIBCXX_3.4.31 versioned symbol

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108969 Romain Geissler changed: What|Removed |Added CC||romain.geissler at amadeus dot com

[Bug libstdc++/109602] Import Gentoo msgfmt patch ?

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109602 --- Comment #5 from Romain Geissler --- Hi, My intention was to try to raise upstream an issue that people packaging gcc may hit in some cases. Gentoo has such a patch, but I also have a similar one on my side since couple of years, it's only

[Bug libstdc++/109602] New: Import Gentoo msgfmt patch ?

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109602 Bug ID: 109602 Summary: Import Gentoo msgfmt patch ? Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++

[Bug tree-optimization/106238] Inline optimization causes dangling pointer on "include/c++/12.1.0/bits/stl_tree.h"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106238 --- Comment #7 from Romain Geissler --- Another case in real life code base (in this case Boost): https://github.com/boostorg/algorithm/pull/113

[Bug tree-optimization/106238] Inline optimization causes dangling pointer on "include/c++/12.1.0/bits/stl_tree.h"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106238 --- Comment #6 from Romain Geissler --- Hi, After upgrading to the latest gcc trunk, I have hit another variant of this problem. For people just willing to exchange containers with swap, just swapping the arguments makes it work, and actually

[Bug tree-optimization/107608] [13 Regression] Failure on fold-overflow-1.c and pr95115.c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107608 --- Comment #34 from Romain Geissler --- >From what I wrote here https://sourceware.org/pipermail/libc-alpha/2022-November/143633.html apparently I already tried gcc 12 back in end of november 2022 and all float issues in glibc testsuite were

[Bug tree-optimization/107608] [13 Regression] Failure on fold-overflow-1.c and pr95115.c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107608 --- Comment #32 from Romain Geissler --- Hi, Thanks for the fix, indeed it has fixed quite some glibc maths tests ;) FYI, most likely it's totally unrelated to this bug, for right now with latest gcc trunk and glibc trunk on x86-64, I still

[Bug tree-optimization/108374] [12/13 Regression] unexpected -Wstringop-overflow when using std::atomic and std::shared_ptr

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108374 --- Comment #1 from Romain Geissler --- I forgot to mention: this happens on x86-64 with -O1.

[Bug tree-optimization/108374] New: [12/13 Regression] unexpected -Wstringop-overflow when using std::atomic and std::shared_ptr

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108374 Bug ID: 108374 Summary: [12/13 Regression] unexpected -Wstringop-overflow when using std::atomic and std::shared_ptr Product: gcc Version: unknown Status: UNCONFIRMED

[Bug tree-optimization/106238] Inline optimization causes dangling pointer on "include/c++/12.1.0/bits/stl_tree.h"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106238 Romain Geissler changed: What|Removed |Added CC||romain.geissler at amadeus dot com

[Bug c++/108165] -Wdangling-reference false positive

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108165 --- Comment #3 from Romain Geissler --- In my real life case B was std::string and used a "string literal" at call site, and I guess using the implicit conversion from const char[] to std::string is something that might happen in many call

[Bug c++/108165] New: -Wdangling-reference false positive

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108165 Bug ID: 108165 Summary: -Wdangling-reference false positive Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++

[Bug c++/108077] [13 Regression] Can't brace initialize container of llvm::opt::OptSpecifier

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

[Bug c++/108077] New: [13 Regression] Can't brace initialize container of llvm::opt::OptSpecifier

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108077 Bug ID: 108077 Summary: [13 Regression] Can't brace initialize container of llvm::opt::OptSpecifier Product: gcc Version: 13.0 Status: UNCONFIRMED Severity:

[Bug driver/107954] New: Support -std=c23/gnu23 as aliases of -std=c2x/gnu2x

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107954 Bug ID: 107954 Summary: Support -std=c23/gnu23 as aliases of -std=c2x/gnu2x Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug tree-optimization/107569] [13 Regression] Failure to optimize std::isfinite since r13-3596

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107569 Romain Geissler changed: What|Removed |Added CC||romain.geissler at amadeus dot com

[Bug c++/102730] New: Consistency of deprecation warning emission with type alias

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102730 Bug ID: 102730 Summary: Consistency of deprecation warning emission with type alias Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal

[Bug libstdc++/100630] Unexpected implicit conversion from volatile bool& to std::filesystem::path in gcc <= 10

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100630 --- Comment #5 from Romain Geissler --- Hi, Thanks for providing a fix that quickly ! I backported it in my own copy of gcc 8 and 9 and it fixed my issue on these branches as well. Cheers, Romain

[Bug libstdc++/100630] New: Unexpected implicit conversion from volatile bool& to std::filesystem::path in gcc <= 10

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100630 Bug ID: 100630 Summary: Unexpected implicit conversion from volatile bool& to std::filesystem::path in gcc <= 10 Product: gcc Version: 10.3.0 Status: UNCONFIRMED

[Bug c++/93821] Define __cplusplus to 202002L in C++20

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93821 Romain Geissler changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Bug middle-end/98465] Bogus warning stringop-overread wuth -std=gnu++20 -O2 and std::string::insert

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98465 --- Comment #3 from Romain Geissler --- I have found another example in my code base raising this error: #include std::string f1() { std::string aString = "string"; aString = "bigger str"; return aString; } With: -O2

[Bug middle-end/98465] Bogus warning stringop-overread wuth -std=gnu++20 -O2 and std::string::insert

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98465 --- Comment #2 from Romain Geissler --- Hi Martin, Thanks for your investigation. I have a few questions: - Since the warning seems to be fully emitted by system headers, shouldn't it be silenced by default ? Why isn't it the case here ? On

[Bug c++/98463] [11 Regression] internal compiler error: in output_constructor_regular_field, at varasm.c:5491 by r11-2720

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98463 --- Comment #3 from Romain Geissler --- Hi, While I initially flagged this as a regression in gcc 11, it's indeed a latent gcc bug which predates gcc 11. What makes it for my specific test case a regression is because now tuple use

[Bug middle-end/98465] New: Bogus warning stringop-overread wuth -std=gnu++20 -O2 and std::string::insert

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98465 Bug ID: 98465 Summary: Bogus warning stringop-overread wuth -std=gnu++20 -O2 and std::string::insert Product: gcc Version: 11.0 Status: UNCONFIRMED Severity:

[Bug c++/98463] New: [11 Regression] internal compiler error: in output_constructor_regular_field, at varasm.c:5491

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98463 Bug ID: 98463 Summary: [11 Regression] internal compiler error: in output_constructor_regular_field, at varasm.c:5491 Product: gcc Version: 11.0 Status: UNCONFIRMED

[Bug ipa/98106] New: gcc trunk miscompiles glibc dynamic loader

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98106 Bug ID: 98106 Summary: gcc trunk miscompiles glibc dynamic loader Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: ipa

[Bug libstdc++/97758] New: bits/std_function.h: error: unknown type name 'type_info' when using -fno-exceptions -fno-rtti

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97758 Bug ID: 97758 Summary: bits/std_function.h: error: unknown type name 'type_info' when using -fno-exceptions -fno-rtti Product: gcc Version: 11.0 Status: UNCONFIRMED