public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Kewen Lin <linkw@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r12-6429] rs6000: Remove useless code related to -mno-power10
Date: Tue, 11 Jan 2022 03:27:49 +0000 (GMT)	[thread overview]
Message-ID: <20220111032749.6F8E8385840E@sourceware.org> (raw)

https://gcc.gnu.org/g:2e1116c5f5af7166c9689b5421f607b814778de7

commit r12-6429-g2e1116c5f5af7166c9689b5421f607b814778de7
Author: Kewen Lin <linkw@linux.ibm.com>
Date:   Mon Jan 10 20:39:33 2022 -0600

    rs6000: Remove useless code related to -mno-power10
    
    Option -mpower10 was made as "WarnRemoved" since commit r11-2318,
    so -mno-power10 doesn't take effect any more.  This patch is to
    remove one line code which respects it.
    
    gcc/ChangeLog:
    
            * config/rs6000/rs6000.c (rs6000_disable_incompatible_switches): Remove
            useless related to option -mno-power10.

Diff:
---
 gcc/config/rs6000/rs6000.c | 1 -
 1 file changed, 1 deletion(-)

diff --git a/gcc/config/rs6000/rs6000.c b/gcc/config/rs6000/rs6000.c
index 319182e94d9..f4c7d836f40 100644
--- a/gcc/config/rs6000/rs6000.c
+++ b/gcc/config/rs6000/rs6000.c
@@ -24834,7 +24834,6 @@ rs6000_disable_incompatible_switches (void)
     const HOST_WIDE_INT dep_flags;	/* flags that depend on this option.  */
     const char *const name;		/* name of the switch.  */
   } flags[] = {
-    { OPTION_MASK_POWER10,	OTHER_POWER10_MASKS,	"power10"	},
     { OPTION_MASK_P9_VECTOR,	OTHER_P9_VECTOR_MASKS,	"power9-vector"	},
     { OPTION_MASK_P8_VECTOR,	OTHER_P8_VECTOR_MASKS,	"power8-vector"	},
     { OPTION_MASK_VSX,		OTHER_VSX_VECTOR_MASKS,	"vsx"		},


                 reply	other threads:[~2022-01-11  3:27 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=20220111032749.6F8E8385840E@sourceware.org \
    --to=linkw@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).