On 9/23/19 4:42 PM, Peter Maydell wrote:
> On Mon, 23 Sep 2019 at 15:40, Philippe Mathieu-Daudé
> wrote:
>> So currently there is no MIPS-I only CPU.
>> Note that the code got written with MIPS32 in mind, and implementing
>> MIPS-I requires a considerable amount of change in the codebase.
>
> ..
On Mon, 23 Sep 2019 at 15:40, Philippe Mathieu-Daudé wrote:
> So currently there is no MIPS-I only CPU.
> Note that the code got written with MIPS32 in mind, and implementing
> MIPS-I requires a considerable amount of change in the codebase.
...but MIPS-I binaries should run on MIPS-II and newer
Hi Libo,
On 9/23/19 10:15 AM, Libo Zhou wrote:
> Hi all,
>
> I have an binary file generated by a cross compiler. The 'file' command says
>
> $ file test
> test: ELF 32-bit LSB LSB executable, MIPS, MIPS-I version 1 (SYSV),
> statically linked, with debug_info, not stripped.
If you look at the
On Mon, 23 Sep 2019 at 13:08, Libo Zhou wrote:
>
> Any help guys? Is there a way to look at the ELF binary code to see if the
> instructions have invalid encoding scheme? Since I used a custom compiler
> that claims to have MIPS-I instructions. I doubt it though because 'file'
> command gives a
Hi all,
I have an binary file generated by a cross compiler. The 'file' command says
$ file test
test: ELF 32-bit LSB LSB executable, MIPS, MIPS-I version 1 (SYSV), statically
linked, with debug_info, not stripped.
When I executed it with
$./qemu-mipsel test
qemu: uncaught target signal 4 (Ill