mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Jaydeep Patil <Jaydeep.Patil@imgtec.com>
To: "musl@lists.openwall.com" <musl@lists.openwall.com>,
	Szabolcs Nagy <nsz@port70.net>
Cc: Andre McCurdy <armccurdy@gmail.com>
Subject: RE: [MUSL] microMIPS32R2 O32 port
Date: Fri, 21 Apr 2017 09:40:45 +0000	[thread overview]
Message-ID: <BD7773622145634B952E5B54ACA8E349DAE2D5DC@PUMAIL01.pu.imgtec.org> (raw)
In-Reply-To: <BD7773622145634B952E5B54ACA8E349DAE2CAB5@PUMAIL01.pu.imgtec.org>

Hi Szabolcs,

Could you please commit this patch?

Thanks,
Jaydeep

>-----Original Message-----
>From: Jaydeep Patil [mailto:Jaydeep.Patil@imgtec.com]
>Sent: 13 April 2017 PM 04:07
>To: Szabolcs Nagy; musl@lists.openwall.com
>Cc: Andre McCurdy
>Subject: RE: [musl] [MUSL] microMIPS32R2 O32 port
>
>Hi Szabolcs,
>
>Please find the attached patch.
>
>Thanks,
>Jaydeep
>
>>-----Original Message-----
>>From: Szabolcs Nagy [mailto:nsz@port70.net]
>>Sent: 13 April 2017 PM 02:31
>>To: musl@lists.openwall.com
>>Cc: Andre McCurdy; Jaydeep Patil
>>Subject: Re: [musl] [MUSL] microMIPS32R2 O32 port
>>
>>* Jaydeep Patil <Jaydeep.Patil@imgtec.com> [2017-04-13 04:29:10 +0000]:
>>> With this branch (micromips32r2_v2) we are supporting microMIPS cores
>>that co-exist with MIPS. The MUSL library must be built with
>>-minterlink- compressed option as there are couple of hand-written MIPS
>only functions.
>>For microMIPS only cores we will create a different subarch.
>>>
>>
>>ok the _v2 branch makes sense to me
>>(the patch is sufficiently small that
>>you can send it to the list)
>>
>>i think i was looking at _v1 before
>>
>>> >-----Original Message-----
>>> >From: Andre McCurdy [mailto:armccurdy@gmail.com]
>>> >Sent: 13 April 2017 AM 03:17
>>> >To: musl@lists.openwall.com
>>> >Cc: Jaydeep Patil
>>> >Subject: Re: [musl] [MUSL] microMIPS32R2 O32 port
>>> >
>>> >On Wed, Apr 12, 2017 at 1:27 PM, Rich Felker <dalias@libc.org> wrote:
>>> >> On Wed, Apr 12, 2017 at 09:25:35PM +0200, Szabolcs Nagy wrote:
>>> >>> * 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?
>>> >>
>>> >> Yes, it's something like thumb or thumb2 on arm, or the riscv
>>> >> compressed isa. What I'm not clear on is whether there are
>>> >> micromips-only cpu models that can't execute normal mips.
>>> >
>>> >According to:
>>> >
>>> >  https://imagination-technologies-cloudfront-
>>>
>>>assets.s3.amazonaws.com/documentation/MIPS_Architecture_microMIPS
>3
>>2
>>> >_InstructionSet_AFP_P_MD00582_06.04.pdf
>>> >
>>> >"microMIPS is also an alternative to the MIPS(r) instruction
>>> >encoding and can be implemented in parallel or stand-alone."
>>> >
>>> >"If only one ISA mode exists (either MIPS or microMIPS) then this
>>> >mode switch mechanism does not exist"
>>> >
>>> >> If so we probably need the ability to build musl as micromips, but
>>> >> as long as cpus which support both support interworking (calls
>>> >> between the two type of code in the same process) reasonably, I
>>> >> don't think there's any reason to consider it a different subarch.
>>> >>
>>> >> If not (that is, if all cpus that support micromips also support
>>> >> the normal mips isa) then I fail to see why there's any need to
>>> >> compile musl's asm files as micromips. They're not size or
>>> >> performance bottlenecks.
>>> >>
>>> >> Rich


  reply	other threads:[~2017-04-21  9:40 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
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 [this message]
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=BD7773622145634B952E5B54ACA8E349DAE2D5DC@PUMAIL01.pu.imgtec.org \
    --to=jaydeep.patil@imgtec.com \
    --cc=armccurdy@gmail.com \
    --cc=musl@lists.openwall.com \
    --cc=nsz@port70.net \
    /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).