[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BD7773622145634B952E5B54ACA8E349DAE2C7C6@PUMAIL01.pu.imgtec.org>
Date: Wed, 12 Apr 2017 11:54:10 +0000
From: Jaydeep Patil <Jaydeep.Patil@...tec.com>
To: "musl@...ts.openwall.com" <musl@...ts.openwall.com>
Subject: RE: microMIPS32R2 O32 port
Hi Rich,
We can reuse existing MIPS code for microMIPS. There are places where we read from $ra must be compiled for MIPS.
Please refer to https://github.com/JaydeepIMG/musl-1/tree/micromips32r2_v2 for modifications.
Thanks,
Jaydeep
>-----Original Message-----
>From: Rich Felker [mailto:dalias@...ifal.cx] On Behalf Of Rich Felker
>Sent: 07 April 2017 PM 07:50
>To: musl@...ts.openwall.com
>Subject: Re: [musl] [MUSL] microMIPS32R2 O32 port
>
>On Fri, Apr 07, 2017 at 06:47:57AM +0000, Jaydeep Patil wrote:
>> Hi Rich,
>>
>> microMIPS is an Application Specific Extension (ASE) to MIPS cores.
>> Both microMIPS and MIPS can co-exist. MIPS code can call microMIPS and
>> vice-versa. microMIPS is a compressed ISA and contains both 16 and
>> 32-bit instructions for code size benefit.
>
>In that case I'm confused what the benefit of compiling the asm files as
>micromips rather than plain mips is. Is it just to save 10 bytes here and there?
>
>Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
