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 debug/109237] csmith: another timeout with -g -O3 this time since r12-156-g8d4c374c4419a875
Date: Wed, 19 Apr 2023 08:30:06 +0000	[thread overview]
Message-ID: <bug-109237-4-xfp8GrVs4K@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109237-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #13 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:8f81100115f68b37fb2723e987c14a3185d1f47d

commit r14-60-g8f81100115f68b37fb2723e987c14a3185d1f47d
Author: Richard Biener <rguenther@suse.de>
Date:   Wed Mar 22 10:05:19 2023 +0100

    rtl-optimization/109237 - speedup bb_is_just_return

    For the testcase bb_is_just_return is on top of the profile, changing
    it to walk BB insns backwards puts it off the profile.  That's because
    in the forward walk you have to process possibly many debug insns
    but in a backward walk you very likely run into control insns first.

            PR rtl-optimization/109237
            * cfgcleanup.cc (bb_is_just_return): Walk insns backwards.

--- Comment #14 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:675ac8822b51a39f6a66a44858d7c31ece8700f2

commit r14-61-g675ac8822b51a39f6a66a44858d7c31ece8700f2
Author: Richard Biener <rguenther@suse.de>
Date:   Wed Mar 22 09:29:49 2023 +0100

    rtl-optimization/109237 - quadraticness in delete_trivially_dead_insns

    The following addresses quadraticness in processing debug insns
    in delete_trivially_dead_insns and insn_live_p by using TREE_VISITED
    on the INSN_VAR_LOCATION_DECL to indicate a later debug bind
    with the same decl and no intervening real insn or debug marker.
    That gets rid of the NEXT_INSN walk in insn_live_p in favor of
    first clearing TREE_VISITED in the first loop over insn and
    the book-keeping of decls we set the bit since we need to clear
    them when visiting a real or debug marker insn.

    That improves the time spent in delete_trivially_dead_insns from
    10.6s to 2.2s for the testcase.

            PR rtl-optimization/109237
            * cse.cc (insn_live_p): Remove NEXT_INSN walk, instead check
            TREE_VISITED on INSN_VAR_LOCATION_DECL.
            (delete_trivially_dead_insns): Maintain TREE_VISITED on
            active debug bind INSN_VAR_LOCATION_DECL.

  parent reply	other threads:[~2023-04-19  8:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-21 17:04 [Bug c/109237] New: csmith: another timeout with -g -O3 this time dcb314 at hotmail dot com
2023-03-21 18:00 ` [Bug middle-end/109237] " dcb314 at hotmail dot com
2023-03-21 20:04 ` pinskia at gcc dot gnu.org
2023-03-21 20:12 ` pinskia at gcc dot gnu.org
2023-03-21 20:26 ` [Bug debug/109237] " pinskia at gcc dot gnu.org
2023-03-22  7:36 ` rguenth at gcc dot gnu.org
2023-03-22  7:52 ` rguenth at gcc dot gnu.org
2023-03-22  8:34 ` rguenth at gcc dot gnu.org
2023-03-22  9:02 ` [Bug debug/109237] csmith: another timeout with -g -O3 this time since r12-156-g8d4c374c4419a875 marxin at gcc dot gnu.org
2023-03-22  9:11 ` rguenth at gcc dot gnu.org
2023-03-22  9:59 ` rguenth at gcc dot gnu.org
2023-03-27  6:57 ` cvs-commit at gcc dot gnu.org
2023-03-27  6:59 ` rguenth at gcc dot gnu.org
2023-04-19  8:30 ` cvs-commit at gcc dot gnu.org [this message]
2023-04-19  9:21 ` rguenth at gcc dot gnu.org
2023-07-10  8:53 ` 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-109237-4-xfp8GrVs4K@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).