From: Jens Gustedt <jens.gustedt@inria.fr>
To: musl@lists.openwall.com
Subject: Re: [PATCH 2/3] Have different definitions of __pthread_tsd_main agree in size
Date: Mon, 11 Feb 2013 15:07:28 +0100 [thread overview]
Message-ID: <1360591648.9132.117.camel@eris.loria.fr> (raw)
In-Reply-To: <20130211134454.GR20323@brightrain.aerifal.cx>
[-- Attachment #1: Type: text/plain, Size: 1466 bytes --]
Am Montag, den 11.02.2013, 08:44 -0500 schrieb Rich Felker:
> The current intended usage is that __environ is used in ISO C
> functions and startup code that must not reference the name environ
> (since it's in the namespace reserved for the application), and POSIX
> and extension functions use environ.
If this was the intended use, the effective use was not in line with
it. execv and execvp had it differently.
> There's no reason the latter
> _need_ to use environ though; it was just more convenient and less
> implementation-specific. If you think there's a good reason to change
> it after reading this, let's discuss it.
With what I have added in my other mail (and you have snipped :) in
the current model there is even the danger that environ and __environ
split into two different objects.
char **environ;
int main(void) {
return (long)&environ;
}
When compile-linking this with musl I get both symbols environ and
__environ linked in.
So it would at least be good that the internal use of it in musl would
be consistent and the C library would not see two distinct objects.
Jens
--
:: INRIA Nancy Grand Est :: http://www.loria.fr/~gustedt/ ::
:: AlGorille ::::::::::::::: office Nancy : +33 383593090 ::
:: ICube :::::::::::::: office Strasbourg : +33 368854536 ::
:: ::::::::::::::::::::::::::: gsm France : +33 651400183 ::
:: :::::::::::::::::::: gsm international : +49 15737185122 ::
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-02-11 14:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-10 22:32 Jens Gustedt
2013-02-11 0:31 ` Rich Felker
2013-02-11 7:40 ` Jens Gustedt
2013-02-11 11:22 ` Szabolcs Nagy
2013-02-11 12:08 ` Szabolcs Nagy
2013-02-11 12:51 ` Jens Gustedt
2013-02-11 13:09 ` Szabolcs Nagy
2013-02-11 13:38 ` Jens Gustedt
2013-02-11 13:44 ` Rich Felker
2013-02-11 14:07 ` Jens Gustedt [this message]
2013-02-11 14:39 ` Szabolcs Nagy
2013-02-11 16:30 ` Jens Gustedt
2013-02-11 17:08 ` Szabolcs Nagy
2013-02-11 17:21 ` Jens Gustedt
2013-02-11 21:49 ` Rich Felker
2013-02-11 21:47 ` Rich Felker
2013-02-11 21:50 ` 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=1360591648.9132.117.camel@eris.loria.fr \
--to=jens.gustedt@inria.fr \
--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).