[Bug target/109665] Incorrect code generation for s390/s390x try-catch (__cxa_begin_catch), causing SIGSEGV

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109665 --- Comment #3 from Paul Groke --- Created attachment 54952 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54952&action=edit Minimal repro Added minimal repro

[Bug target/109665] Incorrect code generation for s390/s390x try-catch (__cxa_begin_catch), causing SIGSEGV

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109665 --- Comment #2 from Paul Groke --- -fno-schedule-insns and/or -fno-schedule-insns2 don't change the instruction sequence for calling __cxa_begin_catch. BTW: for compiler versions present there, it's super easy to check this with godbolt.org. Ju

[Bug c++/109665] New: Incorrect code generation for s390/s390x try-catch (__cxa_begin_catch), causing SIGSEGV

Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: paul.groke at dynatrace dot com Target Milestone: --- In certain situations, GCC generates incorrect s390x code for calling `__cxa_begin_catch`. The bogus code

[Bug libstdc++/54185] [4.7/4.8 Regression] condition_variable not properly destructed

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54185 Paul Groke changed: What|Removed |Added CC||paul.groke at dynatrace dot com

[Bug c++/82270] incorrect warning [-Wignored-attributes]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82270 Paul Groke changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|DUPLICATE

[Bug libstdc++/98376] this_thread::sleep_for(short duration) can sleep forever on Linux

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98376 --- Comment #2 from Paul Groke --- I was able to reproduce the problem with the following program (see below). It won't reproduce well on a loaded machine and you may have to fiddle with the spin counts to get a successful repro. I know this is

[Bug libstdc++/98376] this_thread::sleep_for(short duration) can sleep forever on Linux

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98376 --- Comment #1 from Paul Groke --- Sorry, I only realized that using links to master doesn't make much sense after I had already created the ticket. Those links should be stable: https://github.com/golang/proposal/blob/5b63da9579c3b19294be614dc

[Bug libstdc++/98376] New: this_thread::sleep_for(short duration) can sleep forever on Linux

Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: paul.groke at dynatrace dot com Target Milestone: --- If libstdc++ is configured with _GLIBCXX_USE_NANOSLEEP (which seems to be the case on most systems), it will use nanosleep in

[Bug c++/93901] New: noexcept specifier on ctor does not work with constexpr variable or expression

: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: paul.groke at dynatrace dot com Target Milestone: --- Seems like with GCC 10, only the literal `true` works as expected in noexcept specifiers for ctors. Other expressions

[Bug c++/82270] incorrect warning [-Wignored-attributes]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82270 --- Comment #2 from Paul Groke --- I've contributed a workaround to Boost that avoids the bogus warning when using boost::container::small_vector: https://github.com/boostorg/move/pull/14 So if whoever fixes this wants to test with boost::contai

[Bug c++/82270] New: incorrect warning [-Wignored-attributes]

++ Assignee: unassigned at gcc dot gnu.org Reporter: paul.groke at dynatrace dot com Target Milestone: --- Created attachment 42210 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=42210&action=edit Reproducer GCC version 6.4, SPARC 32 and 64 bit System: Solaris No comma