From: "Frank Ch. Eigler" <fche@redhat.com>
To: Joern Rennecke <joernr@arc.com>
Cc: cgen@sources.redhat.com
Subject: Re: delayed branches and zero overhead loops
Date: Tue, 13 Feb 2007 18:51:00 -0000 [thread overview]
Message-ID: <20070213185118.GA20088@redhat.com> (raw)
In-Reply-To: <20070213153717.GA12710@elsdt-razorfish.arc.com>
Hi -
> The ARCompact architecture has delay slots and zero overhead loops.
> I see that there is already a cgen simulator with delay slots, for
> the iq2000. I've looked at its mloop.in xextract-pbb case [...]
For what it's worth, my recollection about how the PBB stuff works is
so hazy that I won't be able to give quick good advice. Have you
considered using a plain non-pbb kernel, where you can hand-code these
subtleties in plain C/C++ code?
- FChE
next prev parent reply other threads:[~2007-02-13 18:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-13 15:37 Joern Rennecke
2007-02-13 18:51 ` Frank Ch. Eigler [this message]
2007-02-13 21:00 ` Joern Rennecke
2007-02-13 21:12 ` Frank Ch. Eigler
2007-02-13 22:21 ` Joern Rennecke
2007-02-14 17:09 ` Dave Brolley
2007-02-14 18:30 ` Joern Rennecke
2007-02-14 19:52 ` Dave Brolley
2007-02-14 20:15 ` Joern Rennecke
2007-02-16 20:54 ` Dave Brolley
2007-02-19 3:39 ` Joern Rennecke
[not found] ` <45D9C06A.4030903@redhat.com>
2007-02-19 15:56 ` Joern Rennecke
2007-02-19 16:07 ` Frank Ch. Eigler
2007-02-19 18:14 ` Joern Rennecke
2007-02-19 18:19 ` Dave Brolley
2007-02-22 15:50 ` Joern Rennecke
2007-02-22 16:08 ` insert evaluation for multi-ifields broken Joern Rennecke
2007-02-22 16:56 ` Dave Brolley
2007-02-22 18:14 ` Joern Rennecke
2007-02-23 17:45 ` Dave Brolley
2007-02-15 16:54 ` delayed branches and zero overhead loops Joern Rennecke
2007-02-14 18:58 ` decode-bitsize (Was: Re: delayed branches and zero overhead loops) Joern Rennecke
2007-02-13 19:25 ` delayed branches and zero overhead loops Doug Evans
2007-02-13 20:38 ` Joern Rennecke
2007-02-14 18:30 ` Doug Evans
2007-02-14 19:22 ` 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=20070213185118.GA20088@redhat.com \
--to=fche@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=joernr@arc.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).