mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: Broken silent glibc-specific assumptions uncovered by musl
Date: Sun, 19 May 2013 20:23:19 -0400	[thread overview]
Message-ID: <20130520002319.GM20323@brightrain.aerifal.cx> (raw)
In-Reply-To: <20130520001705.GB1075@port70.net>

On Mon, May 20, 2013 at 02:17:05AM +0200, Szabolcs Nagy wrote:
> * Rich Felker <dalias@aerifal.cx> [2013-05-19 18:08:32 -0400]:
> > On Sun, May 19, 2013 at 12:51:47AM +0200, Szabolcs Nagy wrote:
> > > CHARSET (toutf8)
> > 
> > What is toutf8? (Just curious)
> > 
> 
> it is in libidn
> "toutf8.c --- Convert strings from system locale into UTF-8."

Oh. Speaking of which, we need to add IDN support at some point...

> > > here (i386) constructors are put into .ctors.* sections
> > > which get sorted by the linker
> > 
> > How does this work for dynamic linking? Is priority only respected
> > within a single DSO, and not between multiple DSOs?
> 
> i think ordering is only guaranteed within a single dso
> and this is not clearly documented

Yes, I think that's the only approach that makes sense anyway. And it
makes the whole ctor-priority system even more ugly because it causes
program semantics to change depending on how the program is broken up
into shared libraries, counteracting all the hard work ELF did to make
dynamic linking transparent with respect to program semantics...

Rich


      reply	other threads:[~2013-05-20  0:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-17 17:37 Rich Felker
2013-05-18  9:18 ` Szabolcs Nagy
2013-05-18  9:31   ` Daniel Cegiełka
2013-05-18 14:15   ` Rich Felker
2013-05-18 22:51     ` Szabolcs Nagy
2013-05-19 22:08       ` Rich Felker
2013-05-20  0:17         ` Szabolcs Nagy
2013-05-20  0:23           ` Rich Felker [this message]

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=20130520002319.GM20323@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).