mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Masanori Ogino <masanori.ogino@gmail.com>
To: lowrisc-dev@lists.lowrisc.org
Cc: musl@lists.openwall.com
Subject: [GSoC] Porting musl libc to RISC-V
Date: Wed, 27 Apr 2016 11:06:55 +0900	[thread overview]
Message-ID: <CAA-4+jeVL+T3otgi+aQZQM_PRY4Y+N1J5804nDyNCuEajk6KOw@mail.gmail.com> (raw)

Hello,

I'm a master's student in Japan majoring in informatics. In this year,
my proposal for lowRISC has been accepted as part of Google Summer of
Code, so I'd like to introduce myself and the project I will work on.
You may have already discussed with me on the mailing lists, though
:-)

The goal of my project is completing a RISC-V port of musl
(http://www.musl-libc.org/), mentored by Rich Felker. I hope the
project could benefit the RISC-V community. Since musl has been used
by some lightweight/embedded Linux distributions including Alpine
Linux and OpenWrt, the project will be attractive especially for
embedded system developers, I guess.

The project aims not only adding RV-specific part of the libc, but
also integrating it into the toolchain. I also consider some
improvements to the kernel side interacting with libc (e.g. migrating
compare-and-swap emulation from system calls to vDSO functions) if
possible.

For details, you can get my proposal on GitHub:
https://github.com/omasanori/gsoc2016-proposal

I'm definitely new to the community though I have had interest in both
RISC-V and musl for years. Nice to meet you!

Any comments would be appreciated. I hope you will get excited at this
project too.

-- 
Masanori Ogino


             reply	other threads:[~2016-04-27  2:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-27  2:06 Masanori Ogino [this message]
2016-04-29  4:11 ` Rich Felker
2016-05-03 13:15   ` Masanori Ogino

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=CAA-4+jeVL+T3otgi+aQZQM_PRY4Y+N1J5804nDyNCuEajk6KOw@mail.gmail.com \
    --to=masanori.ogino@gmail.com \
    --cc=lowrisc-dev@lists.lowrisc.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).