mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Harald Becker <ralda@gmx.de>
Cc: musl@lists.openwall.com, dalias@aerifal.cx
Subject: Re: Current status: important changes since 0.9.11
Date: Fri, 19 Jul 2013 20:39:23 +0200	[thread overview]
Message-ID: <20130719203923.1a411332@ralda.gmx.de> (raw)
In-Reply-To: <20130719161234.GA8335@brightrain.aerifal.cx>

Hi Rich !

> Oh, and the new crt1.c idea could probably go in too, even
> though it won't be used much yet except possibly adding PIE
> support on mips, powerpc, and microblaze.

I looked at your new crt1.c and I like it. Why not using it for
main stream purpose if it works for all purposes? Are there any
troubles or caveats except a few bytes more (and some nanoseconds
of extra CPU time on program startup)? This doesn't look so
critical. It seams more to me, you need to look for stuff not
needed to be linked in, especially for carefully written and
statically linked small programs, using only base functions. IMO
there shall be a possibility to get those programs smaller (not
linking in some unused library stuff). The few bytes more of
startup code doesn't really matter for this, and you save a lot
of work, when only using one kind of startup routines.

So I would convert all versions to new startup type, then do
testing and push it in release. With a possible backup directory
(unmaintained) for old startup routines (in case anybody needs).
If no one complains, remove this backup directory in next release
or one after.

Just my cent on this topic. As I'm a programmer who like to
create small statically linked programs.

--
Harald


  reply	other threads:[~2013-07-19 18:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-19 16:12 Rich Felker
2013-07-19 18:39 ` Harald Becker [this message]
2013-07-19 18:53   ` Rich Felker
2013-07-19 19:40     ` Harald Becker
2013-07-19 19:49     ` Luca Barbato
2013-07-19 19:54       ` Rich Felker
2013-07-19 20:19         ` Luca Barbato
2013-07-19 20:26           ` Rich Felker
2013-07-19 20:36             ` Luca Barbato
2013-07-22  4:57 ` idunham

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=20130719203923.1a411332@ralda.gmx.de \
    --to=ralda@gmx.de \
    --cc=dalias@aerifal.cx \
    --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).