[Bug tree-optimization/115049] [14/15 Regression] Silent severe miscompilation around inline functions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115049 --- Comment #4 from Jörn Heusipp --- Using '-Q --help=optimizers' to verify, "-O2" is equivalent to " -O1 \ -falign-functions=16 \ -falign-jumps=16:11:8 \ -falign-labels=0:0:8 \ -falign-loops=16:11:8 \ -fcaller-saves \ -fcode-hoisting \ -fcrossj

[Bug tree-optimization/115049] [14/15 Regression] Silent severe miscompilation around inline functions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115049 --- Comment #3 from Jörn Heusipp --- Created attachment 58613 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58613&action=edit updated testcase-v2 Updated testcase that got rid of std::mt19937. It's still somewhat huge because it still dr

[Bug c++/115049] New: Silent severe miscompilation around inline functions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115049 Bug ID: 115049 Summary: Silent severe miscompilation around inline functions Product: gcc Version: 14.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Comp

[Bug c++/109455] New: false-positive -Wstringop-overflow warning when using std::vector with UBsan

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109455 Bug ID: 109455 Summary: false-positive -Wstringop-overflow warning when using std::vector with UBsan Product: gcc Version: 12.2.0 Status: UNCONFIRMED Severity:

[Bug c++/108013] `extern "C" int t = 1;` warns about being declared as extern and initialized

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108013 --- Comment #1 from Jörn Heusipp --- Thanks for the work-around with using a extern "C" {} block. That's actually way better than the extra .c file that I did use.

[Bug c/45977] "warning: 'i' initialized and declared 'extern'" could use a separate warning flag controlling it

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=45977 Jörn Heusipp changed: What|Removed |Added CC||manx-bugzilla@problemloesun

[Bug driver/103949] gcc fails to provide a standard conforming C11 or C++17 environment even when specifying -std=c11 or -std=c++17

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103949 --- Comment #17 from Jörn Heusipp --- (In reply to Jonathan Wakely from comment #9) > (In reply to Jörn Heusipp from comment #8) > > > Note in newer versions of glibc, libpthread is all intergrated into libc > > > and > > > there is no issues

[Bug driver/103949] gcc fails to provide a standard conforming C11 or C++17 environment even when specifying -std=c11 or -std=c++17

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103949 --- Comment #15 from Jörn Heusipp --- (In reply to Jonathan Wakely from comment #14) > What is the output of x86_64-w64-mingw32-g++-posix -v manx@appendix:~$ x86_64-w64-mingw32-g++-posix -v Using built-in specs. COLLECT_GCC=x86_64-w64-mingw32-g

[Bug driver/103949] gcc fails to provide a standard conforming C11 or C++17 environment even when specifying -std=c11 or -std=c++17

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103949 --- Comment #13 from Jörn Heusipp --- (In reply to Jonathan Wakely from comment #10) > Oh I missed the part about __STDCPP_THREADS__ not being defined for > mingw-w64. That seems like it's worth a distinct bug report that can focus > just on th

[Bug driver/103949] gcc fails to provide a standard conforming C11 or C++17 environment even when specifying -std=c11 or -std=c++17

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103949 --- Comment #8 from Jörn Heusipp --- > Note in newer versions of glibc, libpthread is all intergrated into libc and > there is no issues again. > > For Mac OS X/darwin you don't need -lm -pthread because libc has it. Two examples where it wor

[Bug driver/103949] gcc fails to provide a standard conforming C11 or C++17 environment even when specifying -std=c11 or -std=c++17

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103949 Jörn Heusipp changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|INVALID

[Bug driver/103949] New: gcc fails to provide a standard conforming C11 or C++17 environment even when specifying -std=c11 or -std=c++17

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103949 Bug ID: 103949 Summary: gcc fails to provide a standard conforming C11 or C++17 environment even when specifying -std=c11 or -std=c++17 Product: gcc Version: unk

[Bug c++/103826] Bogus shift-negative-value warning in C++20 mode

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103826 --- Comment #2 from Jörn Heusipp --- (In reply to Andrew Pinski from comment #1) > Note I notice clang warns about: > int main() { > return (0x7000') << 4; > } It's valid, but clang complains here about shifting bits out of the range o

[Bug c++/103826] New: Bogus shift-negative-value warning in C++20 mode

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103826 Bug ID: 103826 Summary: Bogus shift-negative-value warning in C++20 mode Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: