From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Cc: Jaydeep Patil <Jaydeep.Patil@imgtec.com>
Subject: Re: [MUSL] microMIPS32R2 O32 port
Date: Wed, 12 Apr 2017 21:25:35 +0200 [thread overview]
Message-ID: <20170412192535.GG2082@port70.net> (raw)
In-Reply-To: <BD7773622145634B952E5B54ACA8E349DAE2C7C6@PUMAIL01.pu.imgtec.org>
* Jaydeep Patil <Jaydeep.Patil@imgtec.com> [2017-04-12 11:54:10 +0000]:
> 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.
>
is micromips a different encoding for mips instructions
that works on some cpus but not others?
does it require musl changes because micromips does not
support all mips instructions just a subset?
> Thanks,
> Jaydeep
>
> >-----Original Message-----
> >From: Rich Felker [mailto:dalias@aerifal.cx] On Behalf Of Rich Felker
> >Sent: 07 April 2017 PM 07:50
> >To: musl@lists.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
next prev parent reply other threads:[~2017-04-12 19:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-05 6:33 Jaydeep Patil
2017-04-06 16:18 ` dalias
2017-04-07 6:47 ` Jaydeep Patil
2017-04-07 14:19 ` Rich Felker
2017-04-12 11:54 ` Jaydeep Patil
2017-04-12 19:25 ` Szabolcs Nagy [this message]
2017-04-12 20:27 ` Rich Felker
2017-04-12 21:47 ` Andre McCurdy
2017-04-13 4:29 ` Jaydeep Patil
2017-04-13 9:00 ` Szabolcs Nagy
2017-04-13 10:37 ` Jaydeep Patil
2017-04-21 9:40 ` Jaydeep Patil
2017-04-21 13:33 ` Rich Felker
2017-04-24 5:30 ` Jaydeep Patil
2017-04-24 13:48 ` Rich Felker
2017-04-25 4:45 ` Jaydeep Patil
2017-04-25 16:52 ` Rich Felker
2017-04-26 7:14 ` Jaydeep Patil
2017-05-11 3:25 ` Jaydeep Patil
2017-05-17 8:28 ` Jaydeep Patil
2017-05-26 3:46 ` Jaydeep Patil
2017-05-28 2:00 ` Rich Felker
2017-05-31 13:11 ` Rich Felker
2017-06-01 4:21 ` Jaydeep Patil
2017-04-21 13:26 ` Rich Felker
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=20170412192535.GG2082@port70.net \
--to=nsz@port70.net \
--cc=Jaydeep.Patil@imgtec.com \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).