public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Iain D Sandoe <iains@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-3777] libgcc, X86: Adjust guard for Mach-O code. Date: Wed, 22 Sep 2021 07:01:39 +0000 (GMT) [thread overview] Message-ID: <20210922070139.9E1823858D39@sourceware.org> (raw) https://gcc.gnu.org/g:578b76873383784841f5478573f4ac5d251aa0ba commit r12-3777-g578b76873383784841f5478573f4ac5d251aa0ba Author: Iain Sandoe <iain@sandoe.co.uk> Date: Wed Sep 22 07:42:21 2021 +0100 libgcc, X86: Adjust guard for Mach-O code. Existing code in the sfp-machine header has been using __MACH__ as a guard for Mach-O, where currently symbols aliases are not supported. __MACH__ is not a sufficient guard for this, since the define is also emitted for HURD, at least. Fixed by amending the guard to use __APPLE__ instead. Signed-off-by: Iain Sandoe <iain@sandoe.co.uk> libgcc/ChangeLog: * config/i386/sfp-machine.h: Guard Mach-O-specific code using __APPLE__. Diff: --- libgcc/config/i386/sfp-machine.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libgcc/config/i386/sfp-machine.h b/libgcc/config/i386/sfp-machine.h index 172ebc70c8d..c451ae71923 100644 --- a/libgcc/config/i386/sfp-machine.h +++ b/libgcc/config/i386/sfp-machine.h @@ -74,7 +74,7 @@ void __sfp_handle_exceptions (int); #define __BYTE_ORDER __LITTLE_ENDIAN /* Define ALIASNAME as a strong alias for NAME. */ -#if defined __MACH__ +#if defined __APPLE__ /* Mach-O doesn't support aliasing, so we build a secondary function for the alias - we need to do a bit of a dance to find out what the type of the arguments is and then apply that to the secondary function.
reply other threads:[~2021-09-22 7:01 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210922070139.9E1823858D39@sourceware.org \ --to=iains@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).