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 middle-end/105629] [13 Regression] g++.dg/opt/pr94589-2.C for cris, m68k, s390x Date: Tue, 24 May 2022 06:20:20 +0000 [thread overview] Message-ID: <bug-105629-4-rSGoajDU6l@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105629-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105629 --- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:d918faea1217596877a35c4946500399731fbbd3 commit r13-722-gd918faea1217596877a35c4946500399731fbbd3 Author: Richard Biener <rguenther@suse.de> Date: Mon May 23 11:41:50 2022 +0200 tree-optimization/105629 - spaceship recognition regression With the extra GENERIC folding we now do to (unsigned int) __v._M_value & 1 != (unsigned int) __v._M_value we end up with a sign-extending conversion to unsigned int rather than the sign-conversion to unsigned char we expect. Relaxing that fixes the regression. 2022-05-23 Richard Biener <rguenther@suse.de> PR tree-optimization/105629 * tree-ssa-phiopt.cc (spaceship_replacement): Allow a sign-extending conversion.
next prev parent reply other threads:[~2022-05-24 6:20 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-17 15:22 [Bug middle-end/105629] New: " hp at gcc dot gnu.org 2022-05-18 12:37 ` [Bug middle-end/105629] " rguenth at gcc dot gnu.org 2022-05-19 22:40 ` hp at gcc dot gnu.org 2022-05-20 6:07 ` rguenther at suse dot de 2022-05-20 11:43 ` hp at gcc dot gnu.org 2022-05-20 11:46 ` rguenther at suse dot de 2022-05-20 21:55 ` hp at gcc dot gnu.org 2022-05-21 1:26 ` hp at gcc dot gnu.org 2022-05-23 9:15 ` rguenth at gcc dot gnu.org 2022-05-24 6:20 ` cvs-commit at gcc dot gnu.org [this message] 2022-05-24 6:21 ` rguenth at gcc dot gnu.org 2022-05-24 14:02 ` hp 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-105629-4-rSGoajDU6l@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: linkBe 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).