public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/93264] [10 Regression] ICE in cfg_layout_redirect_edge_and_branch_force, at cfgrtl.c:4522
Date: Thu, 02 Apr 2020 12:32:07 +0000	[thread overview]
Message-ID: <bug-93264-4-I3XO7l7dIq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-93264-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from Richard Biener <rguenth at gcc dot gnu.org> ---
Makes me wonder if hot/cold splitting should use a special jump instruction
for crossing jumps which we could fixup/split very late so we see

 (parallel
    (set reg (label_ref ..))
    (set pc (reg))
    (clobber reg))

or something like that.  That is, make sure the crossing jump, if
indirect, has the destination computation easily accessible and
replaceable.

  parent reply	other threads:[~2020-04-02 12:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-93264-4@http.gcc.gnu.org/bugzilla/>
2020-04-02 11:44 ` rguenth at gcc dot gnu.org
2020-04-02 12:10 ` jakub at gcc dot gnu.org
2020-04-02 12:26 ` rguenth at gcc dot gnu.org
2020-04-02 12:32 ` rguenth at gcc dot gnu.org [this message]
2020-04-02 13:55 ` zhroma at gcc dot gnu.org
2020-04-03  8:12 ` rguenth at gcc dot gnu.org
2020-04-03  8:15 ` rguenth at gcc dot gnu.org
2020-04-03 10:13 ` jakub at gcc dot gnu.org
2020-04-03 10:21 ` jakub at gcc dot gnu.org
2020-04-09 12:20 ` rguenth at gcc dot gnu.org
2021-04-27 11:38 ` [Bug rtl-optimization/93264] [10/11/12 " jakub at gcc dot gnu.org
2021-07-28  7:04 ` rguenth at gcc dot gnu.org
2022-04-21  7:47 ` rguenth at gcc dot gnu.org
2023-05-29 10:02 ` [Bug rtl-optimization/93264] [10/11/12/13/14 " jakub 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-93264-4-I3XO7l7dIq@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).