[Bug target/108779] New: No option to change thread-pointer location on AArch64

2023-02-13 Thread zach-gcc at cs dot stanford.edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108779 Bug ID: 108779 Summary: No option to change thread-pointer location on AArch64 Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 C

[Bug target/108779] AARCH64 should add an option to change TLS register location to support EL1/EL2/EL3 system registers

2023-02-14 Thread zach-gcc at cs dot stanford.edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108779 --- Comment #5 from zach-gcc at cs dot stanford.edu --- Thanks for the quick response, I've tried it out and it looks good to me!

[Bug d/108842] New: Cannot use enum array with -fno-druntime

2023-02-17 Thread zach-gcc at cs dot stanford.edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108842 Bug ID: 108842 Summary: Cannot use enum array with -fno-druntime Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: d

[Bug analyzer/108935] New: Incorrect warning for infinite recursion

2023-02-26 Thread zach-gcc at cs dot stanford.edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108935 Bug ID: 108935 Summary: Incorrect warning for infinite recursion Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: analyze

[Bug target/108779] AARCH64 should add an option to change TLS register location to support EL1/EL2/EL3 system registers

2023-02-26 Thread zach-gcc at cs dot stanford.edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108779 --- Comment #6 from zach-gcc at cs dot stanford.edu --- Is there any update on when this will be merged? Is this waiting on GCC 13 to be released first?

[Bug target/108779] AARCH64 should add an option to change TLS register location to support EL1/EL2/EL3 system registers

2023-02-26 Thread zach-gcc at cs dot stanford.edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108779 --- Comment #8 from zach-gcc at cs dot stanford.edu --- Alright sounds good, thanks.

[Bug target/110908] New: [aarch64] Internal compiler error when using -ffixed-x30

2023-08-04 Thread zach-gcc at cs dot stanford.edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110908 Bug ID: 110908 Summary: [aarch64] Internal compiler error when using -ffixed-x30 Product: gcc Version: 13.1.0 Status: UNCONFIRMED Severity: normal Pr

[Bug target/110908] [aarch64] Internal compiler error when using -ffixed-x30

2023-08-07 Thread zach-gcc at cs dot stanford.edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110908 --- Comment #5 from zach-gcc at cs dot stanford.edu --- I am implementing software fault isolation on top of GCC and would like for GCC to only ever store addresses in x30. Use of x30 in its link register role is desired (saving/restoring etc. is

[Bug target/110908] [aarch64] Internal compiler error when using -ffixed-x30

2024-05-07 Thread zach-gcc at cs dot stanford.edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110908 --- Comment #6 from zach-gcc at cs dot stanford.edu --- I've resumed using GCC for this project, where I am instrumenting assembly and require that x30 only ever contain addresses (not arbitrary data). I ran into a case where GCC was storing data

[Bug target/110908] [aarch64] Internal compiler error when using -ffixed-x30

2024-11-25 Thread zach-gcc at cs dot stanford.edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110908 --- Comment #7 from zach-gcc at cs dot stanford.edu --- FYI: the behavior requested in this issue used to be supported by LLVM/Clang with the -ffixed-x30 flag, but has now been renamed to -mlr-for-calls-only. See https://clang.llvm.org/docs/Clang