mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Masanori Ogino <masanori.ogino@gmail.com>
To: Alexander Monakov <amonakov@ispras.ru>
Cc: lowrisc-dev@lists.lowrisc.org, musl@lists.openwall.com
Subject: Re: [GSoC2016] A proposal on porting musl to RISC-V
Date: Thu, 17 Mar 2016 20:10:02 +0900	[thread overview]
Message-ID: <CAA-4+jd3Dw_M=gG1GvPD7crxRMsgiz-PEAjC54KThiE8Q0rdaw@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.20.1603161123050.28602@monopod.intra.ispras.ru>

Thank you for reviewing!

2016-03-16 17:37 GMT+09:00 Alexander Monakov <amonakov@ispras.ru>:
> Hi,
>
> On Wed, 16 Mar 2016, Masanori Ogino wrote:
>> I published an early draft of my Google Summer of Code 2016 proposal.
>> You can get the draft from:
>> https://github.com/omasanori/gsoc2016-proposal .
>>
>> Check https://github.com/omasanori/gsoc2016-proposal/releases/tag/rev1
>> if you want a PDF file of this revision.
>
> I think at the moment the source file (proposal.md) is a bit more informative
> because it has references to source code, and, more importantly, some URLs to
> relevant projects such as the simulator and libc-test.  The PDF still has the
> URLs, but they are typeset the same as normal text.

References to the source code are comment for myself so they don't
appear in the text. Is it better to put them in the text?

Certainly it is inconvenient that hyperlinks are typeset normally in
the PDF. I'll fix it.

>> Any comment would be appreciated. Feel free to send comments on MLs or GitHub.
>
> It looks nice.  I have two non-essential comments:
>
> - in week 1 tasks, you point out "Implement the startup code, function
>   prologue and epilogue"; the comment references musl's crt startup code, but
>   I don't see what the prologue/epilogue refer to; normally the compiler emits
>   them, unless I'm misunderstanding what you say;

The "function prologue and epilogue" here refer the initialization and
termination code executed before/after the entry point function, say
main().
I'll reconsider the wording here to make it clearly.

References:
http://gcc.gnu.org/onlinedocs/gccint/Initialization.html
https://blogs.oracle.com/ahl/entry/the_mysteries_of_init
https://dev.gentoo.org/~vapier/crt.txt

> - I think it would be nice if you could add URLs for other risc-v software
>   projects relevant to this work, namely the toolchain porting efforts
>   (riscv-gnu-toolchain?), and perhaps the kernel port if there's a single URL
>   for that (sorry I'm not familiar with RISC-V).

OK, I'll add them.

-- 
Masanori Ogino


  reply	other threads:[~2016-03-17 11:10 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 [this message]
2016-03-18  1:16     ` Masanori Ogino
2016-03-19  6:37 ` [musl] " Rich Felker
2016-03-20  3:13   ` Masanori Ogino
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+jd3Dw_M=gG1GvPD7crxRMsgiz-PEAjC54KThiE8Q0rdaw@mail.gmail.com' \
    --to=masanori.ogino@gmail.com \
    --cc=amonakov@ispras.ru \
    --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).