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 tree-optimization/102659] -O2 vectorization if-conversion produces wrong code for gcc.dg/torture/pr69760.c Date: Mon, 11 Oct 2021 08:57:24 +0000 [thread overview] Message-ID: <bug-102659-4-G44ZUqn15z@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102659-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102659 --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- If you change the testcase as follows the issue pops up at plain -O2 as well diff --git a/gcc/testsuite/gcc.dg/torture/pr69760.c b/gcc/testsuite/gcc.dg/torture/pr69760.c index 53733c7c6a4..47e01ae59bd 100644 --- a/gcc/testsuite/gcc.dg/torture/pr69760.c +++ b/gcc/testsuite/gcc.dg/torture/pr69760.c @@ -1,11 +1,10 @@ /* PR tree-optimization/69760 */ /* { dg-do run { target { { *-*-linux* *-*-gnu* *-*-uclinux* } && mmap } } } */ -/* { dg-options "-O2" } */ #include <unistd.h> #include <sys/mman.h> -__attribute__((noinline, noclone)) void +__attribute__((noinline, noclone)) static void test_func (double *a, int L, int m, int n, int N) { int i, k;
next prev parent reply other threads:[~2021-10-11 8:57 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-09 4:54 [Bug debug/102659] New: [false diagnosis] extra warning info after O2 vectorization " crazylht at gmail dot com 2021-10-11 8:55 ` [Bug tree-optimization/102659] -O2 vectorization if-conversion produces wrong code " rguenth at gcc dot gnu.org 2021-10-11 8:57 ` rguenth at gcc dot gnu.org [this message] 2021-10-11 8:58 ` rguenth at gcc dot gnu.org 2021-10-11 10:31 ` rguenth at gcc dot gnu.org 2021-10-13 11:11 ` cvs-commit at gcc dot gnu.org 2021-10-13 11:12 ` rguenth at gcc dot gnu.org 2021-10-14 12:58 ` cvs-commit 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-102659-4-G44ZUqn15z@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: linkBe 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).