public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Amker.Cheng" <amker.cheng@gmail.com>
To: gcc@gcc.gnu.org, Jeff Law <law@redhat.com>
Subject: Re: Question about filling multi delay slots
Date: Tue, 01 Dec 2009 09:12:00 -0000	[thread overview]
Message-ID: <e8b251c80912010112y4074bc3m456d7edaef56aaa5@mail.gmail.com> (raw)
In-Reply-To: <4B1439CB.6060306@redhat.com>

On Tue, Dec 1, 2009 at 5:31 AM, Jeff Law <law@redhat.com> wrote:
> On 11/25/09 07:34, Amker.Cheng wrote:

>
> First, it's worth noting very few targets support multiple delay slots and
> as a result that code isn't tested nearly as well as handling of single
> delay slots.
>
> I'm pretty sure we assume that the first insn we add to the delay list
> always goes in the first slot, 2nd insn in the 2nd slot and so-on.
>
> Jeff
>
>
>
Thanks for explanation, I will take closer look into at these codes.


-- 
Best Regards.

      reply	other threads:[~2009-12-01  9:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-25 14:34 Amker.Cheng
2009-11-30 21:50 ` Jeff Law
2009-12-01  9:12   ` Amker.Cheng [this message]

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=e8b251c80912010112y4074bc3m456d7edaef56aaa5@mail.gmail.com \
    --to=amker.cheng@gmail.com \
    --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).