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 13:51:24 +0100 [thread overview]
Message-ID: <1360587084.9132.83.camel@eris.loria.fr> (raw)
In-Reply-To: <20130211120816.GC6181@port70.net>
[-- Attachment #1: Type: text/plain, Size: 2320 bytes --]
Am Montag, den 11.02.2013, 13:08 +0100 schrieb Szabolcs Nagy:
> * Szabolcs Nagy <nsz@port70.net> [2013-02-11 12:22:37 +0100]:
> > are you sure about the correctness of these?
> >
> > they seem to be broken to me: weak aliases are not respected
> > and functions are dropped even if there are weak references to
> > them which is bad..
> >
> > eg if sccp is dropped then in any code that does not
> > use pthread, the cancellable syscalls will be broken
> > (if i understand these right)
the weak alias for sccp is dropped in my link for .so since there is
the real sccp symbol that is linked in. (for pad I didn't check, there
are several places with "pad" as names :)
> ah sorry, --gc-sections is for dynamic linking,
> there the weak aliases dont matter
Hm, I don't think that this is for dynamic linking, only.
> and in case of static linking -fdata-sections
> and -ffunction-sections just makes the elfheader
> bigger and the linking slower (sum size of sections
> may be a bit smaller or bigger because of alignment
> things)
Still I have good experience by using it on another library that
defines a lot of weak symbols that aren't used.
The only real problem I have for libmusl.so is "environ", as of my
other patch. There is probably a good reason that this is made
weak. But why must it be realized as an alias? Wouldn't it be
sufficient to just have it as a weak symbol? something like
// implementation header file
extern char **__environ __attribute__((__weak ));
//__environ.c
char **environ __attribute__((__weak )) = 0;
weak_alias(environ, ___environ);
weak_alias(environ, __environ);
weak_alias(environ, _environ);
> so these flags may be useful for building .so
As I said in my previous mail:
> Also I observed that the .so when compiled with -O3 and -flto is
> smaller than with the default build options.
this is true even without the gc-section stuff. So this is perhaps a
thing to consider.
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 12:51 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 [this message]
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
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=1360587084.9132.83.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).