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 rtl-optimization/108086] internal compiler error: in set_accesses, at rtl-ssa/internals.inl:449
Date: Thu, 15 Dec 2022 17:43:25 +0000	[thread overview]
Message-ID: <bug-108086-4-EGfCo9hgds@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108086-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 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:d49b2a3a1dbbe3ac9ae134bc5742be7fdb417d32

commit r13-4723-gd49b2a3a1dbbe3ac9ae134bc5742be7fdb417d32
Author: Richard Biener <rguenther@suse.de>
Date:   Thu Dec 15 13:42:16 2022 +0100

    middle-end/108086 - avoid quadraticness in copy_edges_for_bb

    For the testcase in PR108086 it's visible that we split blocks
    multiple times when inlining and that causes us to adjust the
    block tail stmt BBs multiple times, once for each split.  The
    fix is to walk backwards and split from the tail instead.

    For a reduced testcase this improves compile-time at -O by 4%.

            PR middle-end/108086
            * tree-inline.cc (copy_edges_for_bb): Walk stmts backwards for
            splitting the block to avoid quadratic behavior with setting
            stmts BB on multliple splits.

  parent reply	other threads:[~2022-12-15 17:43 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-13 18:40 [Bug c++/108086] New: " jonas.keller@uni-bielefeld.de
2022-12-13 18:42 ` [Bug c++/108086] " jonas.keller@uni-bielefeld.de
2022-12-13 18:43 ` jonas.keller@uni-bielefeld.de
2022-12-13 18:43 ` jonas.keller@uni-bielefeld.de
2022-12-14  8:35 ` [Bug rtl-optimization/108086] " rguenth at gcc dot gnu.org
2022-12-14  8:47 ` rguenth at gcc dot gnu.org
2022-12-14 10:53 ` marxin at gcc dot gnu.org
2022-12-15 10:30 ` rguenth at gcc dot gnu.org
2022-12-15 10:32 ` cvs-commit at gcc dot gnu.org
2022-12-15 17:43 ` cvs-commit at gcc dot gnu.org [this message]
2022-12-16  8:30 ` cvs-commit at gcc dot gnu.org
2022-12-16  9:29 ` cvs-commit at gcc dot gnu.org
2022-12-16 11:27 ` [Bug rtl-optimization/108086] [11/12/13 Regression] " rguenth at gcc dot gnu.org
2022-12-16 11:32 ` rguenth at gcc dot gnu.org
2022-12-16 12:06 ` cvs-commit at gcc dot gnu.org
2022-12-16 18:21 ` rsandifo at gcc dot gnu.org
2023-02-02 10:41 ` rsandifo at gcc dot gnu.org
2023-02-02 14:53 ` cvs-commit at gcc dot gnu.org
2023-04-03  8:57 ` [Bug rtl-optimization/108086] [11/12 " cvs-commit at gcc dot gnu.org
2023-04-14 13:15 ` [Bug rtl-optimization/108086] [11 " hubicka at gcc dot gnu.org
2023-05-29 10:07 ` jakub at gcc dot gnu.org
2024-02-19 13:43 ` 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-108086-4-EGfCo9hgds@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).