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 tree-optimization/106112] [10/11 Regression] wrong code at -Os and above on x86_64-linux-gnu since r10-2711-g3ed01d5408045d80
Date: Tue, 11 Oct 2022 13:04:24 +0000	[thread overview]
Message-ID: <bug-106112-4-25TdFWtylz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106112-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Richard Biener
<rguenth@gcc.gnu.org>:

https://gcc.gnu.org/g:b7878f05553bcf569a987dff8a7ef8b045b8d26c

commit r11-10303-gb7878f05553bcf569a987dff8a7ef8b045b8d26c
Author: Richard Biener <rguenther@suse.de>
Date:   Tue Jun 28 13:57:29 2022 +0200

    tree-optimization/106112 - fix CSE from wider operation

    The following fixes a mistake in looking up an extended operand
    in the CSE of a truncated operation.

    2022-06-28  Richard Biener  <rguenther@suse.de>

            PR tree-optimization/106112
            * tree-ssa-sccvn.c (valueized_wider_op): Properly extend
            a constant operand according to its type.

            * gcc.dg/torture/pr106112.c: New testcase.

    (cherry picked from commit 2dbb45d6dc0d20dc159b3d8e27ebb6825074827a)

  parent reply	other threads:[~2022-10-11 13:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-28  9:59 [Bug tree-optimization/106112] New: wrong code at -Os and above on x86_64-linux-gnu zhendong.su at inf dot ethz.ch
2022-06-28 10:00 ` [Bug tree-optimization/106112] " zhendong.su at inf dot ethz.ch
2022-06-28 11:13 ` [Bug tree-optimization/106112] [10/11/12/13 Regression] wrong code at -Os and above on x86_64-linux-gnu since r10-2711-g3ed01d5408045d80 marxin at gcc dot gnu.org
2022-06-28 11:54 ` rguenth at gcc dot gnu.org
2022-06-29  9:15 ` cvs-commit at gcc dot gnu.org
2022-06-29  9:18 ` [Bug tree-optimization/106112] [10/11/12 " rguenth at gcc dot gnu.org
2022-07-19 11:38 ` cvs-commit at gcc dot gnu.org
2022-10-11 13:04 ` cvs-commit at gcc dot gnu.org [this message]
2022-10-14 10:47 ` [Bug tree-optimization/106112] [10 " cvs-commit at gcc dot gnu.org
2022-10-14 10:47 ` rguenth 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-106112-4-25TdFWtylz@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).