public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: Jan Hubicka <hubicka@ucw.cz> To: ubizjak at gmail dot com <gcc-bugzilla@gcc.gnu.org> Cc: gcc-bugs@gcc.gnu.org Subject: Re: [Bug target/114232] [14 regression] ICE when building rr-5.7.0 with LTO on x86 Date: Tue, 5 Mar 2024 13:57:47 +0100 [thread overview] Message-ID: <ZecWy9UUETB-oy91@kam.mff.cuni.cz> (raw) In-Reply-To: <bug-114232-4-XwYd945kSS@http.gcc.gnu.org/bugzilla/> Looking at the prototype patch, why need to change also the splitters? My original goal was to use splitters to expand to faster code sequences while having patterns necessary for both variants. This makes it possible to use optimize_insn_for_size/speed and make decisions using BB profile, since we will not ICE if the hotness of BB changes later.
next prev parent reply other threads:[~2024-03-05 12:57 UTC|newest] Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-05 7:04 [Bug target/114232] New: " sjames at gcc dot gnu.org 2024-03-05 7:05 ` [Bug target/114232] " sjames at gcc dot gnu.org 2024-03-05 7:05 ` sjames at gcc dot gnu.org 2024-03-05 7:05 ` sjames at gcc dot gnu.org 2024-03-05 8:24 ` ubizjak at gmail dot com 2024-03-05 8:59 ` ubizjak at gmail dot com 2024-03-05 9:10 ` rguenth at gcc dot gnu.org 2024-03-05 9:12 ` rguenth at gcc dot gnu.org 2024-03-05 9:14 ` rguenth at gcc dot gnu.org 2024-03-05 9:53 ` ubizjak at gmail dot com 2024-03-05 10:30 ` ubizjak at gmail dot com 2024-03-05 10:36 ` rguenth at gcc dot gnu.org 2024-03-05 10:38 ` jakub at gcc dot gnu.org 2024-03-05 10:48 ` ubizjak at gmail dot com 2024-03-05 10:52 ` rguenther at suse dot de 2024-03-05 11:58 ` jakub at gcc dot gnu.org 2024-03-05 12:09 ` ubizjak at gmail dot com 2024-03-05 12:57 ` Jan Hubicka [this message] 2024-03-05 12:21 ` jakub at gcc dot gnu.org 2024-03-05 12:30 ` hubicka at ucw dot cz 2024-03-05 12:49 ` ubizjak at gmail dot com 2024-03-05 12:53 ` jakub at gcc dot gnu.org 2024-03-05 12:57 ` hubicka at ucw dot cz 2024-03-05 13:06 ` rguenther at suse dot de 2024-03-05 13:08 ` ubizjak at gmail dot com 2024-03-05 13:11 ` jakub at gcc dot gnu.org 2024-03-05 13:43 ` ubizjak at gmail dot com 2024-03-05 14:13 ` hubicka at ucw dot cz 2024-03-06 8:47 ` ubizjak at gmail dot com 2024-03-06 19:54 ` cvs-commit at gcc dot gnu.org 2024-03-06 20:10 ` ubizjak at gmail dot com
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=ZecWy9UUETB-oy91@kam.mff.cuni.cz \ --to=hubicka@ucw.cz \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-bugzilla@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).