public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Peter Bergner <bergner@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r14-2036] rust: Update usage of TARGET_AIX to TARGET_AIX_OS Date: Thu, 22 Jun 2023 23:36:29 +0000 (GMT) [thread overview] Message-ID: <20230622233629.ADD5D3858C2D@sourceware.org> (raw) https://gcc.gnu.org/g:8a30775b0d3037123ee540f7b65a736ad49e05ce commit r14-2036-g8a30775b0d3037123ee540f7b65a736ad49e05ce Author: Paul E. Murphy <murphyp@linux.ibm.com> Date: Thu Jun 22 17:57:23 2023 -0500 rust: Update usage of TARGET_AIX to TARGET_AIX_OS This was noticed when fixing the gccgo usage of the macro, the rust usage is very similar. TARGET_AIX is defined as a non-zero value on linux/powerpc64le which may cause unexpected behavior. TARGET_AIX_OS should be used to toggle AIX specific behavior. 2023-06-22 Paul E. Murphy <murphyp@linux.ibm.com> gcc/rust/ * rust-object-export.cc [TARGET_AIX]: Rename and update usage to TARGET_AIX_OS. Diff: --- gcc/rust/rust-object-export.cc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/gcc/rust/rust-object-export.cc b/gcc/rust/rust-object-export.cc index 1143c767784..f9a395f6964 100644 --- a/gcc/rust/rust-object-export.cc +++ b/gcc/rust/rust-object-export.cc @@ -46,8 +46,8 @@ #define RUST_EXPORT_SECTION_NAME ".rust_export" #endif -#ifndef TARGET_AIX -#define TARGET_AIX 0 +#ifndef TARGET_AIX_OS +#define TARGET_AIX_OS 0 #endif /* Return whether or not GCC has reported any errors. */ @@ -91,7 +91,7 @@ rust_write_export_data (const char *bytes, unsigned int size) { gcc_assert (targetm_common.have_named_sections); sec = get_section (RUST_EXPORT_SECTION_NAME, - TARGET_AIX ? SECTION_EXCLUDE : SECTION_DEBUG, NULL); + TARGET_AIX_OS ? SECTION_EXCLUDE : SECTION_DEBUG, NULL); } switch_to_section (sec);
reply other threads:[~2023-06-22 23:36 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=20230622233629.ADD5D3858C2D@sourceware.org \ --to=bergner@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).