[Bug target/118538] throw not caught causing an seg fault rather than a `terminate called after throwing an instance of 'int'` message

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118538 --- Comment #22 from Disservin --- (In reply to Sam James from comment #21) > (In reply to Disservin from comment #20) > > Could you try build a vanilla GCC in the github runner (possibly with > --enable-default-pie or whatever else) and see if

[Bug target/118538] throw not caught causing an seg fault rather than a `terminate called after throwing an instance of 'int'` message

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118538 --- Comment #20 from Disservin --- I just tried the reproduction on a public runner from github using their "ubuntu 24.04 arm" you can see the segmentation fault happening there as well.. https://github.com/Disservin/gcc-bug/actions/runs/135750

[Bug target/118538] throw not caught causing an seg fault rather than a `terminate called after throwing an instance of 'int'` message

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118538 --- Comment #17 from Disservin --- I also tried some previous gcc compiler version, and on g++-11 and prior the program just doesn't terminate.. no output, nothing.. though when invoked through valgrind, an exception is successfully thrown with

[Bug target/118538] throw not caught causing an seg fault rather than a `terminate called after throwing an instance of 'int'` message

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118538 --- Comment #16 from Disservin --- Since the reproduction involves a fairly large array, I checked my configured stack size on the system, which is 8MiB. It also segfaults with a lower value for N like 800, but if I go down to like 500, I get th

[Bug target/118538] throw not caught causing an seg fault rather than a `terminate called after throwing an instance of 'int'` message

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118538 --- Comment #15 from Disservin --- Here's a smaller reproduction btw cat test.cpp && g++ -O0 -std=c++17 -Wall -Wextra -Wpedantic -Wuninitialized -fno-strict-aliasing -fwrapv -g3 test.cpp && ./a.out #include class StreamParser { public: Strea

[Bug target/118538] throw not caught causing an seg fault rather than a `terminate called after throwing an instance of 'int'` message

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118538 --- Comment #12 from Disservin --- (In reply to Sam James from comment #11) > Can't repro with that either. On which platform are you testing this?

[Bug target/118538] throw not caught causing an seg fault rather than a `terminate called after throwing an instance of 'int'` message

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118538 --- Comment #9 from Disservin --- (In reply to Andrew Pinski from comment #8) > I think you should first report this to ubuntu since I can't reproduce it > with all upstream sources of GCC, glibc. I have opened a bug report here, https://bugs.l

[Bug target/118538] throw not caught causing an seg fault rather than a `terminate called after throwing an instance of 'int'` message

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118538 --- Comment #7 from Disservin --- (In reply to Andrew Pinski from comment #6) > Note on the trunk I get: > [apinski@xeond2 upstream-cross-aarch64]$ > QEMU_LD_PREFIX=./install/aarch64-linux-gnu/sysroot/ > ./install-qemu/bin/qemu-aarch64 a.out > t

[Bug target/118538] throw not caught causing an seg fault rather than a `terminate called after throwing an instance of 'int'` message

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118538 Andrew Pinski changed: What|Removed |Added Summary|Miscompilation at -O0 on|throw not caught causing an

[Bug target/118538] Miscompilation at -O0 on aarch64

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118538 --- Comment #4 from Disservin --- (In reply to Andrew Pinski from comment #2) > Does it matter if file exists or is this testing without file existing? This is without the file being present, if it is present then there's no segfault.

[Bug c++/118538] New: Miscompilation on at -O0 on ARM

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118538 Bug ID: 118538 Summary: Miscompilation on at -O0 on ARM Product: gcc Version: 14.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++

[Bug c++/118440] New: Wrong zero initialization with tuple usage

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118440 Bug ID: 118440 Summary: Wrong zero initialization with tuple usage Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++

[Bug sanitizer/118436] New: Bogus Warning in Tuple with empty constructor

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118436 Bug ID: 118436 Summary: Bogus Warning in Tuple with empty constructor Product: gcc Version: 14.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug tree-optimization/113775] New: Bogus Wstringop-overflow in __atomic_load_n combined with sanitizer flags

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113775 Bug ID: 113775 Summary: Bogus Wstringop-overflow in __atomic_load_n combined with sanitizer flags Product: gcc Version: 13.2.1 Status: UNCONFIRMED Severity: no