public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/115372] [15 Regression] RISCV pr97428.c scan-tree-dump-times after r15-812-gc71886f2ca2
Date: Fri, 07 Jun 2024 05:59:30 +0000	[thread overview]
Message-ID: <bug-115372-4-FT4pzC7lSb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-115372-4@http.gcc.gnu.org/bugzilla/>

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |15.0
           Keywords|                            |testsuite-fail
                 CC|                            |rguenth at gcc dot gnu.org
             Target|                            |riscv

--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
I don't remember seeing FAIL: gcc.dg/vect/pr97428.c in the precommit CI, this
one should get one SLP instance and seeing zero means it now fails to SLP on
RISC-V.  With a cross and rv64gcv I don't see this failure (on top of trunk).
Ah, for me it's XFAILed because of ! vect_hw_misalign - do you use additional
flags?  But even adding -mno-strict-align doesn't help.

Oh, the dejagnu harness uses check_effective_target_riscv_v_misalign_ok
which _runs_ a testcase ... which of course fails for my simple cc1 cross
(w/o binutils and w/o qemu set up).  Is the precommit CI any better here?

      parent reply	other threads:[~2024-06-07  5:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-06 17:53 [Bug target/115372] New: " patrick at rivosinc dot com
2024-06-06 18:23 ` [Bug target/115372] " patrick at rivosinc dot com
2024-06-07  5:59 ` rguenth at gcc dot gnu.org [this message]

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-115372-4-FT4pzC7lSb@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).