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/97821] [9/10/11/12 Regression] wrong code with -ftree-vectorize at -O1 on x86_64-pc-linux-gnu by r6-3608
Date: Tue, 01 Feb 2022 15:47:06 +0000	[thread overview]
Message-ID: <bug-97821-4-ebAHmL66U7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97821-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #11 from Richard Biener <rguenth at gcc dot gnu.org> ---
Created attachment 52325
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52325&action=edit
somewhat reduced testcase

Somewhat reduced testcase.

Note there are uninit diagnostics because we jump into the code skipping
initialization for 'bi', 'bf' and 'ax'.  Those might all be false positives
and the partitions we coalesce do not involve those variables (but their
init is conditionally skipped)

Partition 3: size 4 align 4
        bj      k
Partition 2: size 4 align 4
        be      av

  parent reply	other threads:[~2022-02-01 15:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-13 22:17 [Bug tree-optimization/97821] New: wrong code with -ftree-vectorize at -O1 on x86_64-pc-linux-gnu zhendong.su at inf dot ethz.ch
2020-11-14 18:47 ` [Bug tree-optimization/97821] [8/9/10/11 Regression] wrong code with -ftree-vectorize at -O1 on x86_64-pc-linux-gnu by r6-3608 hjl.tools at gmail dot com
2020-11-16 10:26 ` rguenth at gcc dot gnu.org
2020-11-16 10:48 ` rguenth at gcc dot gnu.org
2021-02-03 16:25 ` jakub at gcc dot gnu.org
2021-02-04  9:02 ` rguenth at gcc dot gnu.org
2021-05-14  9:54 ` [Bug tree-optimization/97821] [9/10/11/12 " jakub at gcc dot gnu.org
2021-06-01  8:18 ` rguenth at gcc dot gnu.org
2021-11-09  7:53 ` pinskia at gcc dot gnu.org
2022-01-31 13:09 ` rguenth at gcc dot gnu.org
2022-01-31 14:35 ` rguenth at gcc dot gnu.org
2022-02-01 15:22 ` rguenth at gcc dot gnu.org
2022-02-01 15:47 ` rguenth at gcc dot gnu.org [this message]
2022-02-02  9:00 ` rguenth 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-97821-4-ebAHmL66U7@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).