public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Thomas Schwinge <tschwinge@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r14-10004] GCN: Enable effective-target 'vect_long_long'
Date: Wed, 17 Apr 2024 09:24:28 +0000 (GMT)	[thread overview]
Message-ID: <20240417092428.824513858D37@sourceware.org> (raw)

https://gcc.gnu.org/g:420ece6b2334bcbbd9da905866f2ca77d4b5fdae

commit r14-10004-g420ece6b2334bcbbd9da905866f2ca77d4b5fdae
Author: Thomas Schwinge <tschwinge@baylibre.com>
Date:   Tue Apr 16 14:10:15 2024 +0200

    GCN: Enable effective-target 'vect_long_long'
    
    ... as made apparent by a number of unexpectedly UNSUPPORTED test cases, which
    now all turn into PASS, with just one exception:
    
        PASS: gcc.dg/vect/vect-early-break_124-pr114403.c (test for excess errors)
        PASS: gcc.dg/vect/vect-early-break_124-pr114403.c execution test
        FAIL: gcc.dg/vect/vect-early-break_124-pr114403.c scan-tree-dump vect "LOOP VECTORIZED"
    
    ..., which needs to be looked into, separately.
    
            gcc/testsuite/
            * lib/target-supports.exp (check_effective_target_vect_long_long):
            Enable for GCN.

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

diff --git a/gcc/testsuite/lib/target-supports.exp b/gcc/testsuite/lib/target-supports.exp
index edce672c0e2..938fff9392c 100644
--- a/gcc/testsuite/lib/target-supports.exp
+++ b/gcc/testsuite/lib/target-supports.exp
@@ -7698,7 +7698,8 @@ proc check_effective_target_vect_long_long { } {
 	     || ([istarget riscv*-*-*]
 		 && [check_effective_target_riscv_v])
 	     || ([istarget loongarch*-*-*]
-		 && [check_effective_target_loongarch_sx])}}]
+		 && [check_effective_target_loongarch_sx])
+	     || [istarget amdgcn-*-*] }}]
 }

                 reply	other threads:[~2024-04-17  9:24 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=20240417092428.824513858D37@sourceware.org \
    --to=tschwinge@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).