From: David Daney <ddaney.cavm@gmail.com>
To: Alexis BRENON <abrenon@wyplay.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Immediate branch offset
Date: Fri, 07 Jun 2013 09:25:09 -0700 [thread overview]
Message-ID: <51B20965.3060903@gmail.com> (raw)
In-Reply-To: <51B1B739.7080104@wyplay.com>
On 06/07/2013 03:34 AM, Alexis BRENON wrote:
> Hi everyone,
>
> I'm new on the list, so I'll make a short introduction of me.
> First of all, I'm french, so, please, be indulgent for my english
> mistakes...
> I'm working on the Pypy project, to create a MIPS backend (a MIPS JIT).
>
> To create the JIT, I have to load some MIPS instruction directly in
> memory without passing through a .asm file or else. So, I cannot set
> some labels. So to make some branches, I try to load the equivalent
> instruction of :
> bne $t0, $t1, -8
> to go back, just before the bne instruction, if $t0 and $t1 are equals.
> But when it run, I've got an illegal instruction error.
> To debug, I write a small program in the MARS MIPS simulator with this
> instruction. But when compiling, assembler says me that -8 is an operand
> of incorrect type.
Dump out your program so you can disassemble it with objdump -d (or
dissassemble it with gdb) And verify that the code looks good.
David Daney
> I would like to know if it's possible to make a branch, with an
> immediate offset, or have I to always provide a label ?
>
> I hope my question is clear.
> Thanks for your attention, and for your answer :-p
>
> Alexis BRENON
>
> P.S. I try to go to the IRC channel, but I receive '#mipslinux :Cannot
> send to channel' every time I send message. Is there any particular
> process to join the channel ?
>
>
>
next prev parent reply other threads:[~2013-06-10 11:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 10:34 Immediate branch offset Alexis BRENON
2013-06-07 16:25 ` David Daney [this message]
2013-06-09 14:43 ` Maciej W. Rozycki
2013-06-10 7:18 ` Alexis BRENON
2013-06-10 18:26 ` Maciej W. Rozycki
2013-06-19 9:11 ` Ralf Baechle
2013-06-19 10:56 ` 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=51B20965.3060903@gmail.com \
--to=ddaney.cavm@gmail.com \
--cc=abrenon@wyplay.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