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 middle-end/107485] [10 Regression] gcc-10 ICE with -fnon-call-exception
Date: Tue, 01 Nov 2022 03:51:21 +0000	[thread overview]
Message-ID: <bug-107485-4-L6MHzVbbwG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107485-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://gcc.gnu.org/bugzill
                   |                            |a/show_bug.cgi?id=104450

--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
I suspect this is almost the same issue as reported in PR 104450 or very
similar.

The IR in GCC 10 before veclowering:
  _5 = _2 < _3;

  <bb 3> :
  _4 = VEC_COND_EXPR <_5, { -1, -1, -1, -1 }, { 0, 0, 0, 0 }>;

While the IR in GCC 11:
  _4 = _2 < _3;

  <bb 3> :
  _5 = _4;
  _6 = VEC_COND_EXPR <_5, { -1, -1, -1, -1 }, { 0, 0, 0, 0 }>;

Notice the extra assignment. It is just hiding the issue.

  parent reply	other threads:[~2022-11-01  3:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-01  3:23 [Bug middle-end/107485] New: " spop at gcc dot gnu.org
2022-11-01  3:40 ` [Bug middle-end/107485] " pinskia at gcc dot gnu.org
2022-11-01  3:41 ` [Bug middle-end/107485] [10 Regression] " pinskia at gcc dot gnu.org
2022-11-01  3:51 ` pinskia at gcc dot gnu.org [this message]
2022-11-01  3:56 ` pinskia at gcc dot gnu.org
2022-11-01  3:58 ` pinskia at gcc dot gnu.org
2022-11-05 10:35 ` rguenth at gcc dot gnu.org
2022-11-14 16:18 ` rguenth at gcc dot gnu.org
2022-11-14 18:08 ` cvs-commit at gcc dot gnu.org
2022-11-14 18:15 ` rguenth at gcc dot gnu.org
2022-11-14 19:19 ` spop 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-107485-4-L6MHzVbbwG@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).