public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/114396] [13/14 Regression] Vector: Runtime mismatch at -O2 with -fwrapv since r13-7988-g82919cf4cb2321
Date: Thu, 21 Mar 2024 10:10:19 +0000	[thread overview]
Message-ID: <bug-114396-4-8iUKrYdwJC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114396-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #21 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to JuzheZhong from comment #19)
> I think it's better to add pr114396.c into vect testsuite instead of x86
> target test since it's the bug not only happens on x86.

Actually I think a testcase would be better if it was placed in
gcc.c-torture/execute/ with just `/* { dg-additional-options
"-fno-vect-cost-model" } */` added.

  parent reply	other threads:[~2024-03-21 10:10 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-19 15:37 [Bug target/114396] New: [14] RISC-V rv64gcv vector: Runtime mismatch at -O3 with -fwrapv patrick at rivosinc dot com
2024-03-19 15:40 ` [Bug target/114396] " patrick at rivosinc dot com
2024-03-19 16:58 ` rdapp at gcc dot gnu.org
2024-03-19 17:01 ` rdapp at gcc dot gnu.org
2024-03-19 17:07 ` redi at gcc dot gnu.org
2024-03-19 17:08 ` [Bug target/114396] [14 Regression] Vector: Runtime mismatch at -O2 " patrick at rivosinc dot com
2024-03-19 17:59 ` [Bug tree-optimization/114396] " pinskia at gcc dot gnu.org
2024-03-19 20:48 ` rdapp at gcc dot gnu.org
2024-03-20  6:12 ` rdapp at gcc dot gnu.org
2024-03-20  8:01 ` rguenth at gcc dot gnu.org
2024-03-20 11:10 ` [Bug tree-optimization/114396] [13/14 " sjames at gcc dot gnu.org
2024-03-20 11:12 ` sjames at gcc dot gnu.org
2024-03-20 11:41 ` sjames at gcc dot gnu.org
2024-03-20 11:42 ` [Bug tree-optimization/114396] [13/14 Regression] Vector: Runtime mismatch at -O2 with -fwrapv since r13-7988-g82919cf4cb2321 sjames at gcc dot gnu.org
2024-03-20 11:56 ` rguenth at gcc dot gnu.org
2024-03-20 12:36 ` liuhongt at gcc dot gnu.org
2024-03-20 12:40 ` liuhongt at gcc dot gnu.org
2024-03-21  3:25 ` liuhongt at gcc dot gnu.org
2024-03-21 10:01 ` cvs-commit at gcc dot gnu.org
2024-03-21 10:05 ` juzhe.zhong at rivai dot ai
2024-03-21 10:08 ` liuhongt at gcc dot gnu.org
2024-03-21 10:10 ` pinskia at gcc dot gnu.org [this message]
2024-03-21 11:17 ` cvs-commit at gcc dot gnu.org
2024-03-22  2:16 ` cvs-commit at gcc dot gnu.org
2024-03-22  2:18 ` cvs-commit at gcc dot gnu.org
2024-03-22  2:19 ` liuhongt 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-114396-4-8iUKrYdwJC@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).