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/107493] [13 Regression] Wrong code at -Os on x86_64-linux-gnu since r13-3486-g4c5b116077638277
Date: Mon, 28 Nov 2022 10:17:40 +0000	[thread overview]
Message-ID: <bug-107493-4-g5TVzcBp4i@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107493-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 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:2b293a949c0fbe21e47c4bc99f807dc941c02bb6

commit r13-4357-g2b293a949c0fbe21e47c4bc99f807dc941c02bb6
Author: Richard Biener <rguenther@suse.de>
Date:   Mon Nov 28 10:25:44 2022 +0100

    tree-optimization/107493 - SCEV analysis with conversions

    This shows another case where trying to validate conversions during
    the CHREC SCC analysis fails because said analysis assumes we are
    converting a complete SCC.  Like the constraint on the initial
    conversion seen restrict all conversions handled to sign-changes.

            PR tree-optimization/107493
            * tree-scalar-evolution.cc (scev_dfs::follow_ssa_edge_expr):
            Only handle no-op and sign-changing conversions.

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

  parent reply	other threads:[~2022-11-28 10:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-01 11:49 [Bug c/107493] New: Wrong code at -Os on x86_64-linux-gnu shaohua.li at inf dot ethz.ch
2022-11-01 15:25 ` [Bug tree-optimization/107493] [13 Regression] " pinskia at gcc dot gnu.org
2022-11-01 15:27 ` pinskia at gcc dot gnu.org
2022-11-05 10:37 ` rguenth at gcc dot gnu.org
2022-11-08 13:29 ` rguenth at gcc dot gnu.org
2022-11-21 12:17 ` [Bug tree-optimization/107493] [13 Regression] Wrong code at -Os on x86_64-linux-gnu since r13-3486-g4c5b116077638277 marxin at gcc dot gnu.org
2022-11-22  8:09 ` rguenth at gcc dot gnu.org
2022-11-28 10:17 ` cvs-commit at gcc dot gnu.org [this message]
2022-11-28 10:18 ` 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-107493-4-g5TVzcBp4i@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).