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
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.
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108779
--- Comment #8 from zach-gcc at cs dot stanford.edu ---
Alright sounds good, thanks.
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?
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:
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
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!
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
