From: Rob Landley <rob@landley.net>
To: musl@lists.openwall.com
Cc: musl@lists.openwall.com
Subject: Re: New "portable" crt1.c
Date: Thu, 25 Jul 2013 02:38:08 -0500 [thread overview]
Message-ID: <1374737888.3031.10@driftwood> (raw)
In-Reply-To: <20130719021726.GA19068@brightrain.aerifal.cx> (from dalias@aerifal.cx on Thu Jul 18 21:17:26 2013)
On 07/18/2013 09:17:26 PM, Rich Felker wrote:
> I'm open to comments, but my feeling is that we should keep the
> existing crt asm for archs where it already exists, but replace the
> empty crt1.c with a version based on this approach, and encourage
> using the new approach on all new ports. In the future, if maintaining
> the current asm becomes a burden (e.g. if new requirements are
> introduced) we could remove the existing asm and switch to the C for
> all ports.
The wiki page on porting to new architectures needs some updating. :)
> Rich
Rob
next prev parent reply other threads:[~2013-07-25 7:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-19 2:17 Rich Felker
2013-07-25 7:38 ` Rob Landley [this message]
2013-07-25 7:41 ` Rich Felker
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=1374737888.3031.10@driftwood \
--to=rob@landley.net \
--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).