mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Jens Gustedt <jens.gustedt@inria.fr>
To: musl@lists.openwall.com
Subject: Re: reserved symbol violations
Date: Sat, 02 Aug 2014 18:57:00 +0200	[thread overview]
Message-ID: <1406998620.8274.183.camel@eris.loria.fr> (raw)
In-Reply-To: <20140802163743.GS1674@brightrain.aerifal.cx>

[-- Attachment #1: Type: text/plain, Size: 1162 bytes --]

Am Samstag, den 02.08.2014, 12:37 -0400 schrieb Rich Felker:
> On Sat, Aug 02, 2014 at 06:28:03PM +0200, Jens Gustedt wrote:
> > Hi,
> >  by digging into the symbols that are dragged into a C11 thread
> > executable I noticed that there are some hotspots that should perhaps
> > be worth looking at. I attach a file that summarizes the findings.
> > 
> > One is simple, I'd change the reference to clock_gettime in
> > __timedwait to __clock_gettime.
> 
> That's fine.

ok

> I have no idea how to make it get linked only if both are used, and I
> suspect it's impossible. However, there's no namespace violation here;
> setrlimit and set*id are from POSIX, not ISO C. So it's just excess
> bloat.

Hm, even inside POSIX this is not conforming, I think. POSIX has a
quite precise idea which headers make which symbols visible.

Jens

-- 
:: INRIA Nancy Grand Est ::: AlGorille ::: ICube/ICPS :::
:: ::::::::::::::: office Strasbourg : +33 368854536   ::
:: :::::::::::::::::::::: gsm France : +33 651400183   ::
:: ::::::::::::::: gsm international : +49 15737185122 ::
:: http://icube-icps.unistra.fr/index.php/Jens_Gustedt ::



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2014-08-02 16:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-02 16:28 Jens Gustedt
2014-08-02 16:37 ` Rich Felker
2014-08-02 16:57   ` Jens Gustedt [this message]
2014-08-02 17:34     ` 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=1406998620.8274.183.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).