mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: Rob Landley <rob@landley.net>
Cc: uclibc@uclibc.org, musl@lists.openwall.com
Subject: Re: Segmentation fault in __uClibc_main on m68k
Date: Sat, 30 May 2015 10:59:14 -0400	[thread overview]
Message-ID: <20150530145914.GN17573@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAOS_Y6SycroR31t8QSjREh63DK-vkwwGupXZFBDMpqs9hkqKNQ@mail.gmail.com>

On Sat, May 30, 2015 at 05:12:13AM -0500, Rob Landley wrote:
> On Sat, May 30, 2015 at 3:06 AM, Waldemar Brodkorb <wbx@openadk.org> wrote:
> > Hi,
> > Rob Landley wrote,
> >
> >> Of course somebody did a uclibc-ng fork (bought the domain name and
> >> everything), but I talked to him and his reason for doing it is there
> >> are some obscure targets even glibc doesn't support, and I expect that
> >> as musl grows support for those targets his reasons for doing it will
> >> gradually fade away. *shrug* We'll see.
> >
> > We'll see. In the FPGA world there are four main architectures,
> > NIOS2, ARC, Microblaze and Xtensa. Nios2 and Microblaze are
> > supported by GNU libc. ARC and Xtensa are only supported by
> > uClibc/uClibc-ng. There are nice developers and company's behind.
> >
> > For all the no-MMU architectures or systems there is only one option
> > at the moment. uClibc/uClibc-ng!
> 
> Actually I spent this morning walking Rich through setup of his new
> sh2 nommu board this morning.

Is there an easy way to get started testing nommu Microblaze Linux in
qemu or another emulator? Since musl already has a microblaze target,
it should be easy to support.

Based on my introduction to this stuff so far, the big thing I think
needs work in the nommu scene is getting rid of hackish toolchain
cruft. Flat binary format is a hideous hack and the exact same thing
(binaries built using the standard psABI calling/linking conventions,
but without shareable text) can be achieved with plain (non-FDPIC)
ELF, but the kernel refuses to enable binfmt_elf for nommu, despite
the fact that binfmt_elf_fdpic exists and can do the exact work
binfmt_elf should be doing on nommu when it detects that the ELF
headers require a fixed displacement between LOAD segments.

When we get musl working on nommu, I don't want to dredge back up all
the horrible hacks that were done historically in uclinux. Plain ELF
binaries for the same ISA should just work, albeit with fork() failing
with ENOSYS and some combinations of mmap flags failing, etc., and
with no sharing of text. Then we can gradually add FDPIC on an
as-needed basis. I'm working out the proof-of-concept for this
approach on sh2 right now.

Rich

           reply	other threads:[~2015-05-30 14:59 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CAOS_Y6SycroR31t8QSjREh63DK-vkwwGupXZFBDMpqs9hkqKNQ@mail.gmail.com>]

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=20150530145914.GN17573@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=musl@lists.openwall.com \
    --cc=rob@landley.net \
    --cc=uclibc@uclibc.org \
    /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).