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/103254] [12 Regression] Compile time hog in compare_values_warnv since r12-4790-g4b3a325f07acebf4
Date: Thu, 25 Nov 2021 10:55:21 +0000	[thread overview]
Message-ID: <bug-103254-4-3XkvOP0oOB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103254-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 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:d1c1919ef8a18eea9d5c1741f8c9adaabf5571f2

commit r12-5515-gd1c1919ef8a18eea9d5c1741f8c9adaabf5571f2
Author: Aldy Hernandez <aldyh@redhat.com>
Date:   Wed Nov 24 17:58:43 2021 +0100

    path solver: Move boolean import code to compute_imports.

    In a follow-up patch I will be pruning the set of exported ranges
    within blocks to avoid unnecessary work.  In order to do this, all the
    interesting SSA names must be in the internal import bitmap ahead of
    time.  I had already abstracted them out into compute_imports, but I
    missed the boolean code.  This fixes the oversight.

    There's a net gain of 25 threadable paths, which is unexpected but
    welcome.

    Tested on x86-64 & ppc64le Linux.

    gcc/ChangeLog:

            PR tree-optimization/103254
            * gimple-range-path.cc (path_range_query::compute_ranges): Move
            exported boolean code...
            (path_range_query::compute_imports): ...here.

      parent reply	other threads:[~2021-11-25 10:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-15 17:27 [Bug tree-optimization/103254] New: [12 Regression] Compile time hog in compare_values_warnv asolokha at gmx dot com
2021-11-16  8:18 ` [Bug tree-optimization/103254] [12 Regression] Compile time hog in compare_values_warnv since r12-4790-g4b3a325f07acebf4 marxin at gcc dot gnu.org
2021-11-16 10:11 ` aldyh at gcc dot gnu.org
2021-11-18 16:34 ` amacleod at redhat dot com
2021-11-19 16:43 ` cvs-commit at gcc dot gnu.org
2021-11-19 16:44 ` amacleod at redhat dot com
2021-11-25 10:55 ` cvs-commit at gcc dot gnu.org
2021-11-25 10:55 ` cvs-commit at gcc dot gnu.org [this message]

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-103254-4-3XkvOP0oOB@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).