public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "juzhe.zhong at rivai dot ai" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/112531] [14] RISC-V: gcc.dg/unroll-8.c rtl-dump scan errors with --param=riscv-autovec-preference=scalable
Date: Tue, 14 Nov 2023 22:13:46 +0000	[thread overview]
Message-ID: <bug-112531-4-fAfkYVeYyb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112531-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112531

JuzheZhong <juzhe.zhong at rivai dot ai> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |juzhe.zhong at rivai dot ai

--- Comment #1 from JuzheZhong <juzhe.zhong at rivai dot ai> ---
This FAIL is reasonable. So we can ignore it.

The vectorized code will fail at this dump check like ARM SVE:
https://godbolt.org/z/dbsKb7bxY

Or you can fix testcase like AMDGCN:

disable vectorization:

/* { dg-additional-options "-fno-tree-vectorize" { target amdgcn-*-* } } */

  reply	other threads:[~2023-11-14 22:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-14 19:12 [Bug target/112531] New: " ewlu at rivosinc dot com
2023-11-14 22:13 ` juzhe.zhong at rivai dot ai [this message]
2023-11-15 10:28 ` [Bug target/112531] " rdapp at gcc dot gnu.org
2023-11-15 18:10 ` ewlu at rivosinc dot com
2023-11-15 19:51 ` rdapp at gcc dot gnu.org
2023-11-21 23:28 ` palmer at gcc dot gnu.org
2023-11-26  4:36 ` pinskia at gcc dot gnu.org

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=bug-112531-4-fAfkYVeYyb@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).