mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: mips port working! & remaining issues
Date: Fri, 13 Jul 2012 01:23:13 -0400	[thread overview]
Message-ID: <20120713052313.GA20369@brightrain.aerifal.cx> (raw)

Hi all,

According to libc-testsuite, the new mips port of musl is working. If
remaining issues exist, I suspect they're in the bits/*.h files'
definitions of kernel constants and structures, which I could use some
help reviewing. Threads, including cancellation, are known to work,
and mipsel (little endian) mode presumably works but is untested.

One major omission that remains is the dynamic linker. Due to mips
o32's pathologically bad PIC ABI which has no PC-relative addressing,
the current dynamic linker cannot work as-is. Rather than replacing it
with an ugly mess of fragile early-stage code that depends on
non-optimization by the compiler (the way traditional dynamic linkers
work), I'd rather simply require the dynamic linker and libc to be
loaded at a fixed address chosen at build time -- this is basically
what prelink does. We may be able to use the existing prelink tools,
or just write a small special-purpose tool to prepare libc.so for
loading at a fixed address.

Another major omission shared with arm is that setjmp/longjmp cannot
preserve floating point registers. This is because I don't yet know
how to determine at runtime whether hard-float is available, and the
registers can't be saved unless they can be determined to exist. Help
solving this problem would also be appreciated.

Rich


             reply	other threads:[~2012-07-13  5:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-13  5:23 Rich Felker [this message]
2012-07-13  8:15 ` Szabolcs Nagy
2012-07-13  8:18   ` Justin Cormack
2012-07-13 13:08     ` Rich Felker
2012-07-13 13:36       ` Luca Barbato
2012-07-13 14:25         ` Rich Felker
2012-07-13 16:10           ` Szabolcs Nagy
2012-07-13 17:34             ` Rich Felker
2012-07-13 20:40               ` Szabolcs Nagy
2012-07-13 20:58           ` idunham
2012-07-13 22:18             ` Rich Felker
2012-07-13 15:15 ` Gregor Richards

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=20120713052313.GA20369@brightrain.aerifal.cx \
    --to=dalias@aerifal.cx \
    --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).