Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Thomas Koeller <thomas.koeller@baslerweb.com>
To: linux-mips@linux-mips.org
Cc: "Kevin D. Kissell" <kevink@mips.com>
Subject: Re: jump instruction in delay slot
Date: Tue, 19 Oct 2004 17:48:50 +0200	[thread overview]
Message-ID: <200410191748.50810.thomas.koeller@baslerweb.com> (raw)
In-Reply-To: <000901c4b5e8$70141160$10eca8c0@grendel>

On Tuesday 19 October 2004 16:32, Kevin D. Kissell wrote:

> By default, a MIPS assembler will automatically
> fill delay slots and even move instructions around
> to fill them.  This can be inhibited by the
>     set .noreorder
> directive, of which you'll note there is one in the
> top level tital_handle_int routine, but there's a
>     set .reorder
> at the end of that routine, so by the time it gets to
> the code you're interested in, things should be OK.

I see. I really wonder if there is any up-to-date
documentation covering the mips-specific features
of gas. Have been googling for it, no success so
far.

thanks,
Thomas
-- 
--------------------------------------------------

Thomas Koeller, Software Development

Basler Vision Technologies
An der Strusbek 60-62
22926 Ahrensburg
Germany

Tel +49 (4102) 463-390
Fax +49 (4102) 463-46390

mailto:thomas.koeller@baslerweb.com
http://www.baslerweb.com

==============================

  parent reply	other threads:[~2004-10-19 15:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-19 14:05 jump instruction in delay slot Thomas Koeller
2004-10-19 14:25 ` Thiemo Seufer
     [not found] ` <000901c4b5e8$70141160$10eca8c0@grendel>
2004-10-19 15:48   ` Thomas Koeller [this message]
2004-10-19 17:06 ` Ralf Baechle
     [not found] <B482D8AA59BF244F99AFE7520D74BF961A5B71@server1.RightHand.righthandtech.com>
2004-10-19 17:00 ` Thomas Koeller
2004-10-19 17:02   ` Ralf Baechle

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=200410191748.50810.thomas.koeller@baslerweb.com \
    --to=thomas.koeller@baslerweb.com \
    --cc=kevink@mips.com \
    --cc=linux-mips@linux-mips.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