public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Lehua Ding <lhtin@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r14-5616] RISC-V Regression: Remove scalable compile option
Date: Mon, 20 Nov 2023 11:21:43 +0000 (GMT)	[thread overview]
Message-ID: <20231120112143.885293858CD1@sourceware.org> (raw)

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

commit r14-5616-ga63cbcc52e4490d365cb09d60ba32577b7134c75
Author: Juzhe-Zhong <juzhe.zhong@rivai.ai>
Date:   Mon Nov 20 18:39:10 2023 +0800

    RISC-V Regression: Remove scalable compile option
    
    Since we already set scalable vectorization by default, this flag is redundant.
    
    Also, we are start to full coverage testing with different compile option.
    E.g --param=riscv-autovec-preference=fixed-vlmax.
    To avoid compile option confusion. Remove it.
    
    gcc/testsuite/ChangeLog:
    
            * lib/target-supports.exp: Remove scalable compile option.

Diff:
---
 gcc/testsuite/lib/target-supports.exp | 1 -
 1 file changed, 1 deletion(-)

diff --git a/gcc/testsuite/lib/target-supports.exp b/gcc/testsuite/lib/target-supports.exp
index 4b647d6a88e..f3cd0311e27 100644
--- a/gcc/testsuite/lib/target-supports.exp
+++ b/gcc/testsuite/lib/target-supports.exp
@@ -11564,7 +11564,6 @@ proc check_vect_support_and_set_flags { } {
         set dg-do-what-default run
     } elseif [istarget riscv64-*-*] {
 	if [check_effective_target_riscv_vector_hw] {
-	    lappend DEFAULT_VECTCFLAGS "--param" "riscv-autovec-preference=scalable"
 	    lappend DEFAULT_VECTCFLAGS "--param" "riscv-vector-abi"
 	    set dg-do-what-default run
 	} else {

                 reply	other threads:[~2023-11-20 11:21 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=20231120112143.885293858CD1@sourceware.org \
    --to=lhtin@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).