mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Cc: Jaydeep Patil <Jaydeep.Patil@imgtec.com>
Subject: Re: [MUSL] microMIPS32R2 O32 port
Date: Wed, 12 Apr 2017 16:27:21 -0400	[thread overview]
Message-ID: <20170412202721.GY17319@brightrain.aerifal.cx> (raw)
In-Reply-To: <20170412192535.GG2082@port70.net>

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.

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-12 20:27 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 [this message]
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=20170412202721.GY17319@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --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).