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:58:50 +0000	[thread overview]
Message-ID: <bug-107485-4-N4wpk1KCox@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

--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #4)
> Yes expand_vector_condition needs a similar fix just as PR 104450 did.

Basically the bug is latent even on the trunk still.


Something like:
diff --git a/gcc/tree-vect-generic.cc b/gcc/tree-vect-generic.cc
index 350129555a0..f585d3ddbc4 100644
--- a/gcc/tree-vect-generic.cc
+++ b/gcc/tree-vect-generic.cc
@@ -1044,6 +1044,7 @@ expand_vector_condition (gimple_stmt_iterator *gsi,
bitmap dce_ssa_names)
     {
       assign = dyn_cast<gassign *> (SSA_NAME_DEF_STMT (a));
       if (assign != NULL
+         && !stmt_can_throw_internal (cfun, assign)
          && TREE_CODE_CLASS (gimple_assign_rhs_code (assign)) ==
tcc_comparison)
        {
          a_is_comparison = true;


Should fix the issue ....

  parent reply	other threads:[~2022-11-01  3:58 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
2022-11-01  3:56 ` pinskia at gcc dot gnu.org
2022-11-01  3:58 ` pinskia at gcc dot gnu.org [this message]
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-N4wpk1KCox@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).