public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Christophe Lyon <clyon@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r12-817] arm: remove error in CPP_SPEC when -mlittle-endian and -mbig-endian are used together
Date: Sun, 16 May 2021 13:48:39 +0000 (GMT)	[thread overview]
Message-ID: <20210516134839.514CD384A00F@sourceware.org> (raw)

https://gcc.gnu.org/g:4a322345cab10879162a2ddf659fb0f873ba0182

commit r12-817-g4a322345cab10879162a2ddf659fb0f873ba0182
Author: Christophe Lyon <christophe.lyon@linaro.org>
Date:   Sun May 16 13:48:21 2021 +0000

    arm: remove error in CPP_SPEC when -mlittle-endian and -mbig-endian are used together
    
    arm.h has had this error message since 1997, but it is no longer
    needed since option parsing has been improved: -mXXX-endian is handled
    via arm.opt and updates the BIG_END mask. So, the last
    instance of -mXXX-endian on the command line wins.
    
    Tested on many arm* configurations, with no impact on the testsuite results.
    
    2021-05-16  Christophe Lyon  <christophe.lyon@linaro.org>
    
            gcc/
            * config/arm/arm.h (CPP_SPEC): Remove error message about
            -mlittle-endian/-mbig-endian conflict.

Diff:
---
 gcc/config/arm/arm.h | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/gcc/config/arm/arm.h b/gcc/config/arm/arm.h
index e430e4d50ed..8e5bd579323 100644
--- a/gcc/config/arm/arm.h
+++ b/gcc/config/arm/arm.h
@@ -89,9 +89,7 @@ extern tree arm_bf16_ptr_type_node;
 
 \f
 #undef  CPP_SPEC
-#define CPP_SPEC "%(subtarget_cpp_spec)					\
-%{mbig-endian:%{mlittle-endian:						\
-	%e-mbig-endian and -mlittle-endian may not be used together}}"
+#define CPP_SPEC "%(subtarget_cpp_spec)"
 
 #ifndef CC1_SPEC
 #define CC1_SPEC ""


                 reply	other threads:[~2021-05-16 13:48 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=20210516134839.514CD384A00F@sourceware.org \
    --to=clyon@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: link
Be 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).