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/102511] [12 Regression] GCC produces incorrect code for -O3: first element of the array is skipped after r12-3903
Date: Tue, 28 Sep 2021 09:12:20 +0000	[thread overview]
Message-ID: <bug-102511-4-ZrhWZgy8l3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102511-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Aldy Hernandez <aldyh@gcc.gnu.org>:

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

commit r12-3916-gfb8b72ebb5b0bf40f7dfef9154c42320ce46f2a7
Author: Aldy Hernandez <aldyh@redhat.com>
Date:   Tue Sep 28 09:38:50 2021 +0200

    Return VARYING in range_on_path_entry if nothing found.

    The problem here is that the solver's code solving unknown SSAs on entry
    to a path was returning UNDEFINED if there were no incoming edges to the
    start of the path that were not the function entry block.  This caused a
    cascade of pain down stream.

    Tested on x86-64 Linux.

            PR tree-optimization/102511

    gcc/ChangeLog:

            * gimple-range-path.cc (path_range_query::range_on_path_entry):
            Return VARYING when nothing found.

    gcc/testsuite/ChangeLog:

            * gcc.dg/pr102511.c: New test.
            * gcc.dg/tree-ssa/ssa-dom-thread-14.c: Adjust.

  parent reply	other threads:[~2021-09-28  9:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-28  3:11 [Bug tree-optimization/102511] New: GCC produces incorrect code for -O3: first element of the array is skipped vsevolod.livinskij at frtk dot ru
2021-09-28  4:24 ` [Bug tree-optimization/102511] [12 Regression] " pinskia at gcc dot gnu.org
2021-09-28  4:33 ` pinskia at gcc dot gnu.org
2021-09-28  4:37 ` pinskia at gcc dot gnu.org
2021-09-28  5:23 ` pinskia at gcc dot gnu.org
2021-09-28  5:37 ` [Bug tree-optimization/102511] [12 Regression] GCC produces incorrect code for -O3: first element of the array is skipped after r12-3903 pinskia at gcc dot gnu.org
2021-09-28  7:36 ` aldyh at gcc dot gnu.org
2021-09-28  7:44 ` pinskia at gcc dot gnu.org
2021-09-28  9:12 ` cvs-commit at gcc dot gnu.org [this message]
2021-09-28  9:19 ` aldyh at gcc dot gnu.org
2021-09-28 14:51 ` aldyh 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-102511-4-ZrhWZgy8l3@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).