public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/107336] [10 regression] ICE segfault expand_expr_real_1 on sparc-sun-solaris2.11 with -m32 -mcpu=niagara4 -O3
Date: Fri, 21 Oct 2022 14:10:20 +0000 [thread overview]
Message-ID: <bug-107336-4-bFMPEVvfAl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107336-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107336
--- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Eric Botcazou
<ebotcazou@gcc.gnu.org>:
https://gcc.gnu.org/g:5076eefe23b96279e34351a2a044858bae3251ae
commit r10-11052-g5076eefe23b96279e34351a2a044858bae3251ae
Author: Eric Botcazou <ebotcazou@adacore.com>
Date: Fri Oct 21 15:46:37 2022 +0200
Fix VCOND expansion
Instead of only allowing the signed optab to provide EQ/NE compares, we
allow both here since there seems to be no documented canonicalization.
gcc/
PR target/107336
* optabs.c (expand_vec_cond_expr): Query both VCOND and VCONDU for
EQ and NE.
next prev parent reply other threads:[~2022-10-21 14:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 19:51 [Bug c++/107336] New: [10/11 " andrew at ishiboo dot com
2022-10-20 19:55 ` [Bug target/107336] " pinskia at gcc dot gnu.org
2022-10-20 19:56 ` pinskia at gcc dot gnu.org
2022-10-20 20:15 ` andrew at ishiboo dot com
2022-10-20 23:28 ` [Bug target/107336] [10 " andrew at ishiboo dot com
2022-10-20 23:47 ` ebotcazou at gcc dot gnu.org
2022-10-20 23:48 ` ebotcazou at gcc dot gnu.org
2022-10-21 6:09 ` rguenth at gcc dot gnu.org
2022-10-21 6:09 ` rguenth at gcc dot gnu.org
2022-10-21 12:37 ` andrew at ishiboo dot com
2022-10-21 14:10 ` cvs-commit at gcc dot gnu.org [this message]
2022-10-21 14:11 ` ebotcazou 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-107336-4-bFMPEVvfAl@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).