public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/113431] [14 Regression] Wrong code at -O3
Date: Wed, 28 Feb 2024 14:55:02 +0000	[thread overview]
Message-ID: <bug-113431-4-vXOl1soQ7q@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113431-4@http.gcc.gnu.org/bugzilla/>

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

Rainer Orth <ro at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|FIXED                       |---
             Status|RESOLVED                    |REOPENED

--- Comment #19 from Rainer Orth <ro at gcc dot gnu.org> ---
The SPARC dump suggests

/vol/gcc/src/hg/master/local/gcc/testsuite/gcc.dg/vect/pr113431.c:12:15:
missed:   unsupported unaligned access
/vol/gcc/src/hg/master/local/gcc/testsuite/gcc.dg/vect/pr113431.c:12:15:
missed:   not vectorized: relevant stmt not supported: a[0][1] = _60;

that the tests needs vect_hw_misalign?

  parent reply	other threads:[~2024-02-28 14:55 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-16 21:45 [Bug target/113431] New: [14] RISC-V rv64gcv vector: Runtime mismatch " patrick at rivosinc dot com
2024-01-16 21:46 ` [Bug target/113431] " patrick at rivosinc dot com
2024-01-16 22:37 ` juzhe.zhong at rivai dot ai
2024-01-16 22:57 ` patrick at rivosinc dot com
2024-01-17  1:38 ` juzhe.zhong at rivai dot ai
2024-01-17  1:42 ` patrick at rivosinc dot com
2024-01-17  1:44 ` juzhe.zhong at rivai dot ai
2024-01-17  1:53 ` patrick at rivosinc dot com
2024-01-17  1:56 ` juzhe.zhong at rivai dot ai
2024-01-17  3:33 ` [Bug tree-optimization/113431] [14 Regression] Wrong code " pinskia at gcc dot gnu.org
2024-01-17  8:08 ` rguenth at gcc dot gnu.org
2024-01-17  8:31 ` juzhe.zhong at rivai dot ai
2024-01-17  8:48 ` rguenth at gcc dot gnu.org
2024-01-17 12:34 ` rguenth at gcc dot gnu.org
2024-01-17 12:59 ` rguenth at gcc dot gnu.org
2024-01-18  7:37 ` cvs-commit at gcc dot gnu.org
2024-01-18  7:39 ` rguenth at gcc dot gnu.org
2024-01-19  8:55 ` ro at gcc dot gnu.org
2024-01-19  8:56 ` ro at gcc dot gnu.org
2024-02-28 14:55 ` ro at gcc dot gnu.org [this message]
2024-03-15 14:06 ` jakub at gcc dot gnu.org
2024-03-15 15:42 ` rguenth at gcc dot gnu.org
2024-03-15 15:52 ` cvs-commit at gcc dot gnu.org
2024-03-15 15:53 ` jakub at gcc dot gnu.org
2024-03-19  9:44 ` ro at CeBiTec dot Uni-Bielefeld.DE

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-113431-4-vXOl1soQ7q@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).