[Bug target/102993] -fcf-protection=full produces segfaulting code when targeting 32-bit x86 (i686)

2021-10-29 Thread luke-jr+gccbugs at utopios dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102993 --- Comment #7 from Luke Dashjr --- It's the standard Ubuntu focal g++-mingw-w64-i686 package.

[Bug target/102993] -fcf-protection=full produces segfaulting code when targeting 32-bit x86 (i686)

2021-10-28 Thread luke-jr+gccbugs at utopios dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102993 Luke Dashjr changed: What|Removed |Added Version|7.0 |9.3.0 --- Comment #2 from Luke Dashjr --

[Bug other/102993] New: -mcf-protection=full produces segfaulting code when targeting 32-bit x86 (i686)

2021-10-28 Thread luke-jr+gccbugs at utopios dot org via Gcc-bugs
: normal Priority: P3 Component: other Assignee: unassigned at gcc dot gnu.org Reporter: luke-jr+gccbugs at utopios dot org Target Milestone: --- Generated programs, when throwing(catching?) an exception, jump to address 0 and crash. Instead, the compiler

[Bug target/85915] ABI incompatibility (multiple definition of `__x86_return_thunk') for static libraries, between GCC 7.3.0 and GCC >=7.4.0, caused by -mfunction-return=thunk

2021-09-11 Thread luke-jr+gccbugs at utopios dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85915 --- Comment #16 from Luke Dashjr --- GCC only supports defaults now?

[Bug middle-end/95189] [9/10 Regression] memcmp being wrongly stripped like strcmp

2020-10-09 Thread luke-jr+gccbugs at utopios dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95189 --- Comment #27 from Luke Dashjr --- AFAIK it's complete, but I am not a GCC developer.

[Bug middle-end/95189] [9/10 Regression] memcmp being wrongly stripped like strcmp

2020-10-08 Thread luke-jr+gccbugs at utopios dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95189 --- Comment #25 from Luke Dashjr --- Created attachment 49334 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49334&action=edit Hacky patch to workaround the bug by disabling builtin memcmp always I wrote and am rebuilding my own systems wi

[Bug middle-end/95189] [9/10 Regression] memcmp being wrongly stripped like strcmp

2020-10-07 Thread luke-jr+gccbugs at utopios dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95189 --- Comment #21 from Luke Dashjr --- Not entirely, I think? At least according to the docs: if you wish to enable built-in functions selectively when using -fno-builtin or -ffreestanding, you may define macros such as:

[Bug middle-end/95189] [9/10 Regression] memcmp being wrongly stripped like strcmp

2020-10-05 Thread luke-jr+gccbugs at utopios dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95189 --- Comment #18 from Luke Dashjr --- Someone pointed out to me that the bug metadata says "Known to work: 9.3.0"

[Bug target/85915] ABI incompatibility (multiple definition of `__x86_return_thunk') for static libraries, between GCC 7.3.0 and GCC >=7.4.0, caused by -mfunction-return=thunk

2019-03-16 Thread luke-jr+gccbugs at utopios dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85915 --- Comment #13 from Luke Dashjr --- I run Gentoo, so it compiled it for me (2.27)

[Bug target/85915] ABI incompatibility (multiple definition of `__x86_return_thunk') for static libraries, between GCC 7.3.0 and GCC >=7.4.0, caused by -mfunction-return=thunk

2019-03-16 Thread luke-jr+gccbugs at utopios dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85915 --- Comment #11 from Luke Dashjr --- Simply upgrading to GCC 8.2.0 failed due to the multiple-definition of __x86_return_thunk, so I successfully built only the C compiler with the non-thunking defaults; from there, I rebuilt glibc again without

[Bug target/85915] ABI incompatibility (multiple definition of `__x86_return_thunk') for static libraries, between GCC 7.3.0 and GCC >=7.4.0, caused by -mfunction-return=thunk

2019-03-16 Thread luke-jr+gccbugs at utopios dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85915 Luke Dashjr changed: What|Removed |Added CC||luke-jr+gccbugs at utopios dot org

[Bug c++/67075] Infinite GC loop with ggc-min-expand=0

2015-07-31 Thread luke-jr+gccbugs at utopios dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67075 --- Comment #1 from Luke Dashjr --- Also note: ggc-min-expand=1 seems to successfully workaround this issue (but is non-ideal for low-memory systems).

[Bug c++/67075] New: Infinite GC loop with ggc-min-expand=0

2015-07-31 Thread luke-jr+gccbugs at utopios dot org
++ Assignee: unassigned at gcc dot gnu.org Reporter: luke-jr+gccbugs at utopios dot org Target Milestone: --- Created attachment 36100 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36100&action=edit Preprocessed source code to reproduce loop, compressed On a low-memory