public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Robin Dapp <rdapp@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-6449] s390: Use arch14 instead of z16 for -march=native.
Date: Fri,  3 Mar 2023 15:06:58 +0000 (GMT)	[thread overview]
Message-ID: <20230303150658.8D3163858002@sourceware.org> (raw)

https://gcc.gnu.org/g:da5adab2ae046bed0e2b72466f439f023f697433

commit r13-6449-gda5adab2ae046bed0e2b72466f439f023f697433
Author: Robin Dapp <rdapp@linux.ibm.com>
Date:   Wed Feb 1 19:39:10 2023 +0100

    s390: Use arch14 instead of z16 for -march=native.
    
    When compiling on a system where binutils do not yet support the 'z16'
    name assembling fails with -march=native on a z16 machine.
    Currently, this is interpreted as -march=z16.  This patch uses -march=arch14
    instead.
    
    gcc/ChangeLog:
    
            * config/s390/driver-native.cc (s390_host_detect_local_cpu): Use
            arch14 instead of z16.

Diff:
---
 gcc/config/s390/driver-native.cc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gcc/config/s390/driver-native.cc b/gcc/config/s390/driver-native.cc
index 563da45c7f6..3b9c1e1ca5d 100644
--- a/gcc/config/s390/driver-native.cc
+++ b/gcc/config/s390/driver-native.cc
@@ -125,10 +125,10 @@ s390_host_detect_local_cpu (int argc, const char **argv)
 	      break;
 	    case 0x3931:
 	    case 0x3932:
-	      cpu = "z16";
+	      cpu = "arch14";
 	      break;
 	    default:
-	      cpu = "z16";
+	      cpu = "arch14";
 	      break;
 	    }
 	}

                 reply	other threads:[~2023-03-03 15:06 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=20230303150658.8D3163858002@sourceware.org \
    --to=rdapp@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).