From: Barry Wealand <barry.wealand@lmco.com>
To: gcc@gcc.gnu.org
Cc: "Kancler, Cliff" <cliff.kancler@lmco.com>,
reed@reedkotler.com, "Katyryniuk,
Mike" <mike.katyryniuk@lmco.com>,
"Steigmeyer, Bruce" <bruce.steigmeyer@lmco.com>
Subject: Disqualifying instructions for branch delay slot scheduling
Date: Fri, 26 Mar 2004 04:29:00 -0000 [thread overview]
Message-ID: <40636AEB.77325951@lmco.com> (raw)
Hello -
We're working with a custom MIPS-like architecture, and have discovered
a few bugs in our hardware design. One way that we can work around
these bugs is to modify our GCC toolchain so that it places NOPs after
or before a small number of specific instructions. The approach of
favor seems to be to modify the assembler to change these specific
instructions into two-instruction macros, with the NOP placed before or
after as appropriate. In order for this to be completely effective,
however, we also need to be sure that the compiler never places these
instructions into branch (or jump, or call) delay slots.
Can anybody quickly summarize how one would go about disqualifying
certain specific instructions for branch delay slot scheduling? Any
guidance at all would be greatly appreciated.
Barry Wealand
barry.wealand@lmco.com
next reply other threads:[~2004-03-25 23:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-26 4:29 Barry Wealand [this message]
2004-03-26 15:28 ` Eric Botcazou
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=40636AEB.77325951@lmco.com \
--to=barry.wealand@lmco.com \
--cc=bruce.steigmeyer@lmco.com \
--cc=cliff.kancler@lmco.com \
--cc=gcc@gcc.gnu.org \
--cc=mike.katyryniuk@lmco.com \
--cc=reed@reedkotler.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).