mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: Re: Weekly Report of Porting musl to RISC-V Project #5
Date: Thu, 8 Dec 2016 19:39:02 -0500	[thread overview]
Message-ID: <20161209003902.GQ1555@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAO6-m027RDV+-H9CsTVRYxfxxxT5Jthc3wMR7H26fPfjfHi8Wg@mail.gmail.com>

On Thu, Dec 08, 2016 at 10:36:44PM -0200, Alan Pillay wrote:
> What is the current status of musl on RISC-V?
> This was the last time I heard about it, but it has been many months since.
> Regards.

The student (Masanori Ogino) disappeared and hasn't been in contact
since. I'd really like to follow up and see what we can salvage from
the project, as this is still a big wishlist item.

Rich


> > Hello,
> >
> > Thanks to the folks, I passed the mid-term evaluation. Now it is about
> > time to publish the fifth progress report on porting musl on RISC-V.
> >
> > Last week, the toolchain itself has been built for RISC-V and running
> > on Spike, and libc-test [1] can be executed with it now. I posted the
> > result of tests on [2]. The REPORT.txt file contains all error
> > messages of failed tests, both run-time ones and compile-time ones.
> >
> > Some failures are expected since musl on x86_64 also does the same
> > ones (e.g. errors in src/api/fcntl.c), but there are some unexpected
> > errors too. I guess that the "warning: <the name of a header> is
> > shorter than expected" warning indicates bugs in arch-dependent part
> > of I/O functions or system calls (or kernel?) and it causes syntax
> > errors in the same compilation unit.
> >
> > Moreover, some tests triggers a "signal 11" error (segmentation fault)
> > in libc. I added some logs to [2]. They are bugs in the port,
> > obviously. I am working on them.
> >
> > The good news is, anyway, some results are *better than x86_64*,
> > especially in math functions :-)
> > (probably the cause is the difference in the floating-point precision,
> > though. it is usual in float tests...)
> >
> > It takes long, long time to get but finally I have a (seems-to-be)
> > working test suite for the port. I will continue to debug and fix the
> > port using the result. Stay tuned!
> >
> >
> > [1]: http://nsz.repo.hu/git/?p=libc-test
> > [2]: https://gist.github.com/omasanori/ee828369aea844ac7fdfdc8362953299
> >
> > --
> > Masanori Ogino


  reply	other threads:[~2016-12-09  0:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-09  0:36 Alan Pillay
2016-12-09  0:39 ` Rich Felker [this message]
2016-12-09  1:35   ` Alan Pillay
2016-12-20 13:11     ` Masanori Ogino
2016-12-20 16:08       ` Rich Felker
2017-05-27 23:19 ` [lowrisc-dev] " Michael Clark
2017-05-27 23:24   ` Michael Clark

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=20161209003902.GQ1555@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --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).