public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Iain Buclaw <ibuclaw@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc(refs/users/ibuclaw/heads/darwin)] Darwin, PPC : Fix R13 for PPC64. Date: Thu, 28 Jan 2021 17:32:34 +0000 (GMT) [thread overview] Message-ID: <20210128173234.84999384B106@sourceware.org> (raw) https://gcc.gnu.org/g:f8d53e819350798e3e314db63f070b7c18c3e736 commit f8d53e819350798e3e314db63f070b7c18c3e736 Author: Iain Sandoe <iain@sandoe.co.uk> Date: Fri Dec 11 00:29:42 2020 +0000 Darwin, PPC : Fix R13 for PPC64. We have a somewhat unusual situation in that for PPC64, R13 is both reserved and callee-saved (it is used internally by the pthreads implementation to contain pthread_self). So add R13 to the fixed regs, but also keep it in the callee- saved set. gcc/ChangeLog: * config/rs6000/darwin.h (FIXED_R13): Add for PPC64. (FIRST_SAVED_GP_REGNO): Save from R13 even when it is one of the fixed regs. Diff: --- gcc/config/rs6000/darwin.h | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/gcc/config/rs6000/darwin.h b/gcc/config/rs6000/darwin.h index 42f39e60305..566794af706 100644 --- a/gcc/config/rs6000/darwin.h +++ b/gcc/config/rs6000/darwin.h @@ -203,7 +203,7 @@ /* Make both r2 and r13 available for allocation. */ #define FIXED_R2 0 -#define FIXED_R13 0 +#define FIXED_R13 TARGET_64BIT /* Base register for access to local variables of the function. */ @@ -213,6 +213,9 @@ #undef RS6000_PIC_OFFSET_TABLE_REGNUM #define RS6000_PIC_OFFSET_TABLE_REGNUM 31 +#undef FIRST_SAVED_GP_REGNO +#define FIRST_SAVED_GP_REGNO 13 + /* Darwin's stack must remain 16-byte aligned for both 32 and 64 bit ABIs. */
next reply other threads:[~2021-01-28 17:32 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-28 17:32 Iain Buclaw [this message] 2021-01-30 19:09 Iain Buclaw 2021-03-07 17:02 Iain Buclaw 2021-03-14 22:01 Iain Buclaw 2021-04-10 15:05 Iain Buclaw 2021-04-10 17:01 Iain Buclaw 2021-04-19 18:06 Iain Buclaw 2021-09-17 14:34 Iain Buclaw
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20210128173234.84999384B106@sourceware.org \ --to=ibuclaw@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).