mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: Todo for release?
Date: Wed, 15 Aug 2012 08:36:40 -0400	[thread overview]
Message-ID: <20120815123640.GK27715@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAPLrYETGvq9L-AEcTj9wOqrMtuJ+890WMnucwF_CVuZvNdcQfg@mail.gmail.com>

On Wed, Aug 15, 2012 at 10:55:06AM +0200, Daniel Cegiełka wrote:
> >
> >> - Support for __progname (Daniel)
> >
> > Daniel, any more thoughts on this? Are there lots of programs that
> > want it that can't easily be patched to simply use argv[0] themselves?
> 
> This is not something that is absolutely necessary. __progname quite
> often is used on *BSD and less on Linux (eg. Owl's msulogin,
> popa3d)... but __progname is always easy to fix.

My leaning is to omit it at least for now then.

> Here we have the OpenBSD repo and content /bin directories:
> 
> http://www.openbsd.org/cgi-bin/cvsweb/src/bin/
> 
> And here's a list of programs (from /bin/) that require __progname (70% of all):

This might be a little bit inflated if it includes programs which
detected the presence of __progname at build time and only used it
because of that.

> For __progname  we probably need to modify (asm) files in the musl/crt/.

No, the only thing that belongs there is the minimum code to get argc,
argv, the addresses of main, _init, _fini, and jump to
__libc_start_main. The latter is responsible for things like
__progname. If the code were put in crt1.o, all programs would have a
reference to __progname encoded into them, which is not something
desirable; it would also increase the amount of per-arch code that
must be maintained.

Rich


  parent reply	other threads:[~2012-08-15 12:36 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-13 18:53 Rich Felker
2012-08-13 21:31 ` Szabolcs Nagy
2012-08-13 21:53   ` Rich Felker
2012-08-13 22:06     ` Solar Designer
2012-08-14 15:02       ` Szabolcs Nagy
2012-08-15  0:30         ` Szabolcs Nagy
2012-08-13 22:20   ` Solar Designer
2012-08-14  1:46     ` Rich Felker
2012-08-14  2:13       ` Solar Designer
2012-08-14  2:35         ` Rich Felker
2012-08-14  2:49           ` Solar Designer
2012-08-14  2:58             ` Rich Felker
2012-08-14  3:35               ` Solar Designer
2012-08-14  4:49                 ` Rich Felker
2012-08-15  4:08 ` Rich Felker
2012-08-15  8:55   ` Daniel Cegiełka
2012-08-15 10:20     ` Szabolcs Nagy
2012-08-15 10:53       ` Daniel Cegiełka
2012-08-15 13:10         ` John Spencer
2012-08-15 13:23           ` Daniel Cegiełka
2012-08-15 13:32       ` Szabolcs Nagy
2012-08-15 14:36         ` Rich Felker
2012-08-17  9:49           ` Szabolcs Nagy
2012-08-17 12:10             ` Rich Felker
2012-08-22 17:45               ` Daniel Cegiełka
2012-08-22 18:57                 ` Rich Felker
2012-08-22 19:15                   ` Daniel Cegiełka
2012-08-22 20:24                   ` Richard Pennington
2012-08-22 22:44                     ` Rich Felker
2012-08-15 12:36     ` Rich Felker [this message]
2012-08-15 12:57   ` Luca Barbato
2012-08-15 14:34     ` Rich Felker
2012-08-15 18:28       ` Luca Barbato
2012-08-15 18:35         ` Rich Felker
2012-08-15 21:25         ` Rich Felker
2012-08-16 17:11           ` Luca Barbato
2012-08-15 13:27   ` Richard Pennington
2012-08-15 22:44 ` boris brezillon

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=20120815123640.GK27715@brightrain.aerifal.cx \
    --to=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).