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/112366] ICE in vectorizable_live_operation, at tree-vect-loop.cc:10798
Date: Fri, 03 Nov 2023 10:30:20 +0000	[thread overview]
Message-ID: <bug-112366-4-TzxUNyooet@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112366-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
_33 = (int) rd_27;
...
_103 = _93 ^ _33;      <--- use of _33
...
__asm__("" : "=r" rd_41 : "" tt2_40);
_113 = {rd_27, rd_41};
vect__33.17_123 = (vector(2) int) _113;
_133 = BIT_FIELD_REF <vect__33.17_123, 32, 0>;
_42 = (int) rd_41;

and here's the vector result of the conversion.  The { rd_27, rd_41 }
CTOR can appear only after the last scalar def but there are other
uses of the components earlier.

The other uses are not really constrained in any way, so the assert is
bougs.  I'll just remove it.

Ideally we'd avoid having any scalar ops participating in the SLP that
dominate any of the external defs (as traditionally external defs happen
before the vector code, not interleaved as we have it here after we
build operands from scalar defs from inside the vectorized region).

  parent reply	other threads:[~2023-11-03 10:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-03  8:20 [Bug middle-end/112366] New: " lehua.ding at rivai dot ai
2023-11-03  8:33 ` [Bug tree-optimization/112366] " rguenth at gcc dot gnu.org
2023-11-03 10:18 ` rguenth at gcc dot gnu.org
2023-11-03 10:30 ` rguenth at gcc dot gnu.org [this message]
2023-11-03 11:01 ` cvs-commit at gcc dot gnu.org
2023-11-03 11:02 ` 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-112366-4-TzxUNyooet@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).