public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jim Wilson <wilson@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r12-1198] RISC-V: Enable riscv attributes by default for all riscv targets.
Date: Thu,  3 Jun 2021 20:55:27 +0000 (GMT)	[thread overview]
Message-ID: <20210603205527.E508A3857801@sourceware.org> (raw)

https://gcc.gnu.org/g:3c70b3ca1ef58f302bf8c16d9e7c7bb8626408bf

commit r12-1198-g3c70b3ca1ef58f302bf8c16d9e7c7bb8626408bf
Author: Jim Wilson <jimw@sifive.com>
Date:   Thu Jun 3 13:50:34 2021 -0700

    RISC-V: Enable riscv attributes by default for all riscv targets.
    
    These were only enabled for embedded elf originally because that was
    the safe option, and linux had no obvious use for them.  But now that
    we have new extensions coming like V that affect process state and ABIs,
    the attributes are expected to be useful for linux, and may be required
    by the psABI.  clang already emits them for all riscv targets.
    
            gcc/
            * config.gcc (riscv*-*-*): If --with-riscv-attribute not used,
            turn it on for all riscv targets.

Diff:
---
 gcc/config.gcc | 9 +--------
 1 file changed, 1 insertion(+), 8 deletions(-)

diff --git a/gcc/config.gcc b/gcc/config.gcc
index 92fad8e20ca..6833a6c13d9 100644
--- a/gcc/config.gcc
+++ b/gcc/config.gcc
@@ -4605,14 +4605,7 @@ case "${target}" in
 			tm_defines="${tm_defines} TARGET_RISCV_ATTRIBUTE=0"
 			;;
 		""|default)
-			case "${target}" in
-			riscv*-*-elf*)
-				tm_defines="${tm_defines} TARGET_RISCV_ATTRIBUTE=1"
-				;;
-			*)
-				tm_defines="${tm_defines} TARGET_RISCV_ATTRIBUTE=0"
-				;;
-			esac
+			tm_defines="${tm_defines} TARGET_RISCV_ATTRIBUTE=1"
 			;;
 		*)
 			echo "--with-riscv-attribute=${with_riscv_attribute} is not supported.  The argument must begin with yes, no or default." 1>&2


                 reply	other threads:[~2021-06-03 20:55 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=20210603205527.E508A3857801@sourceware.org \
    --to=wilson@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).