From: Masanori Ogino <masanori.ogino@gmail.com>
To: Rich Felker <dalias@libc.org>
Cc: lowrisc-dev@lists.lowrisc.org, musl@lists.openwall.com
Subject: Re: [GSoC2016] A proposal on porting musl to RISC-V
Date: Sun, 20 Mar 2016 12:13:43 +0900 [thread overview]
Message-ID: <CAA-4+jcCvV03oxCqNYoGsLtiz=Bcj=RfssJUfrx_V_A1N5Qe=w@mail.gmail.com> (raw)
In-Reply-To: <20160319063749.GT21636@brightrain.aerifal.cx>
Thank you for reviewing!
2016-03-19 15:37 GMT+09:00 Rich Felker <dalias@libc.org>:
> Looks very good! Some comments:
>
> In regards to your schedule, do you plan to do both rv32 and rv64 (and
> some 'subarch' ABI variants for both) in parallel from the beginning?
> I think it might make sense to get one (whatever is easiest) to the
> point where you can do some meaningful testing before working on them
> all, but I'd be happy to hear your thoughts on what approach works
> best for you.
Yes, I planed to port 32-bit and 64-bit variant in parallel. However,
now I think that porting one first and then doing the other is better
since this approach can test the toolchain part earlier.
> One thing to keep in mind (not sure if you're aware of it yet) is that
> there's an in-progress port, now linked from the lowrisc.org project
> ideas page, by another student who's interested in applying. Please
> don't be discouraged by that; the reason I'm mentioning it is just
> that I think anyone applying should either be planning to use the work
> that's already done (being careful to properly document authorship) or
> have a good explanation for why they're not going to. For your
> proposal, this probably means greatly reducing the number of weeks to
> be spent on getting the port basically up and running and dedicating
> more time to the extended deliverables.
I didn't aware of that port. Thanks!
I will take a look at it and revise the proposal with my decision.
> That's actually a good thing because I don't think you've allocated as
> much time for the extended deliverables as they might take. For
> example, for the vdso stuff, if you plan to do the actual kernel
> patches, that's going to require familiarizing yourself with kernel
> hacking if you're not already. And hooking it up to GCC for the
> compiler to use with -mno-atomic (rather than just having libc use it
> internally) requires some GCC hacking _and_ establishing some ABI for
> the GCC-generated code to get to the vdso (probably via libc).
Sure. I will reconsider the schedule.
> Hope these comments help, and sorry for not getting back to you
> sooner. I've had a busy week.
No problem. This really helps me.
--
Masanori Ogino
next prev parent reply other threads:[~2016-03-20 3:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 1:22 Masanori Ogino
2016-03-16 8:37 ` Alexander Monakov
2016-03-17 11:10 ` Masanori Ogino
2016-03-18 1:16 ` Masanori Ogino
2016-03-19 6:37 ` [musl] " Rich Felker
2016-03-20 3:13 ` Masanori Ogino [this message]
2016-03-25 5:12 ` 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+jcCvV03oxCqNYoGsLtiz=Bcj=RfssJUfrx_V_A1N5Qe=w@mail.gmail.com' \
--to=masanori.ogino@gmail.com \
--cc=dalias@libc.org \
--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).