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] [11/12/13 Regression] internal compiler error: in set_accesses, at rtl-ssa/internals.inl:449 Date: Fri, 16 Dec 2022 12:06:11 +0000 [thread overview] Message-ID: <bug-108086-4-iG4rb5yJwD@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 #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:da85bfc75024a92b97e60e4436863dd5789786ec commit r13-4743-gda85bfc75024a92b97e60e4436863dd5789786ec Author: Richard Biener <rguenther@suse.de> Date: Fri Dec 16 13:01:40 2022 +0100 middle-end/108086 - avoid unshare_expr when remapping SSA names r0-89280-g129a37fc319db8 added unsharing to remap_ssa_name but that wasn't in the version of the patch posted. That has some non-trivial cost through mostly_copy_tree_r and copy_tree_r but more importantly it doesn't seem to be necessary. I've successfully bootstrapped and tested with an assert we only get tree_node_can_be_shared trees here. Bootstrapped and tested on x86_64-unknown-linux-gnu with all languages. PR middle-end/108086 * tree-inline.cc (remap_ssa_name): Do not unshare the result from the decl_map.
next prev parent reply other threads:[~2022-12-16 12:06 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 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 [this message] 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-iG4rb5yJwD@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: linkBe 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).