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/105528] [11/12/13 Regression] ICE: in expand_expr_real_2, at expr.cc:10290 with -O2 -mavx512f
Date: Mon, 09 May 2022 06:41:35 +0000	[thread overview]
Message-ID: <bug-105528-4-ANUeqdhqrW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105528-4@http.gcc.gnu.org/bugzilla/>

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |compare-debug-failure

--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Even though this is not directly a compare debug failure, it could be if expand
didn't crash.

Note GCC 10.x had:
  _9 = VEC_COND_EXPR <_8 >= { 4294967295, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0 }, { 5, 5, 5, 5, 5, 5, 5, 5, 5, 5, 5, 5, 5, 5, 5, 5 }, { 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 }>;

  parent reply	other threads:[~2022-05-09  6:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-09  6:29 [Bug rtl-optimization/105528] New: " zsojka at seznam dot cz
2022-05-09  6:36 ` [Bug target/105528] " pinskia at gcc dot gnu.org
2022-05-09  6:39 ` [Bug tree-optimization/105528] " pinskia at gcc dot gnu.org
2022-05-09  6:41 ` pinskia at gcc dot gnu.org [this message]
2022-05-09  6:43 ` pinskia at gcc dot gnu.org
2022-05-09  7:03 ` [Bug tree-optimization/105528] [11/12/13 Regression] ICE: in expand_expr_real_2, at expr.cc:10290 with -O2 -mavx512f since r11-8059-g5240c5ca2e2b1f36 marxin at gcc dot gnu.org
2022-05-09  7:52 ` jakub at gcc dot gnu.org
2022-05-09  8:14 ` rguenth at gcc dot gnu.org
2022-05-09  9:58 ` jakub at gcc dot gnu.org
2022-05-09 10:16 ` pinskia at gcc dot gnu.org
2022-05-10 16:34 ` cvs-commit at gcc dot gnu.org
2022-05-10 16:42 ` cvs-commit at gcc dot gnu.org
2022-05-10 16:47 ` cvs-commit at gcc dot gnu.org
2022-05-10 16:49 ` jakub 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-105528-4-ANUeqdhqrW@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).