public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Steven Bosscher <stevenb@suse.de>
To: law@redhat.com
Cc: gcc@gcc.gnu.org
Subject: Re: Delay branch scheduling vs. the CFG
Date: Sun, 13 Nov 2005 21:20:00 -0000	[thread overview]
Message-ID: <200511132220.21202.stevenb@suse.de> (raw)
In-Reply-To: <1131915750.3728.348.camel@slowpoke>

On Sunday 13 November 2005 22:02, Jeffrey A Law wrote:
> No great insights on how to make dbr_schedule CFG aware -- just
> remember that a filled delay slot can represent 3 different cases:
>
>   1. An extension of the block containing the sequence.
>
>   2. An extension of the block at the target of a branch.
>
>   3. An extension of the fall-thru block.
>
>   4. An entirely new basic block on its own.

When can option 4 happen??

Gr.
Steven

  reply	other threads:[~2005-11-13 21:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-13 20:20 Steven Bosscher
2005-11-13 21:02 ` Jeffrey A Law
2005-11-13 21:20   ` Steven Bosscher [this message]
2005-11-13 21:26     ` Jeffrey A Law
2005-11-16 20:07       ` Richard Henderson
2005-11-16 23:19         ` Jeffrey A Law
2005-11-16 22:42 Joern RENNECKE

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=200511132220.21202.stevenb@suse.de \
    --to=stevenb@suse.de \
    --cc=gcc@gcc.gnu.org \
    --cc=law@redhat.com \
    /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).