public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Ulrich Drepper <drepper@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Roland McGrath <roland@redhat.com>,
	Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: [PATCH] Fix non-IA32 build
Date: Tue, 10 Dec 2002 12:23:00 -0000	[thread overview]
Message-ID: <3DF64D67.6070701@redhat.com> (raw)
In-Reply-To: <20021210190249.N1310@sunsite.ms.mff.cuni.cz>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jakub Jelinek wrote:

> Some __libc aliases were missing on various arches.

I'll look at it.


> I'm not sure if it is a good idea to export the new
> pthread wrappers @@GLIBC_2.3.1, because that will mean current programs/libs
> won't use the wrapped syscalls. IMHO it would be much better to export
> them at the versions they have in libc.so. select would be a slight problem,
> since it is usually select@@GLIBC_2.0, but on Alpha it is
> select@@GLIBC_2.1.

We cannot do this.  Since this means newly linked programs will have
references to select@GLIBC_2.0 in libpthread while there was no so
function in libpthread at that time.  The DSO version startup test will
not catch this and only a relocation will fail later on.  That's wrong.

It's not ideal to have the symbols with different versions but it's also
no big problem.  Old code so far survived without the wrappers (and
ideally their behavior shouldn't be changed).  New programs will find
the new definition and add a reference to it.  This is also the desired
behavior, we don't want the reference to fall back to the definition in
libc.

- -- 
- --------------.                        ,-.            444 Castro Street
Ulrich Drepper \    ,-----------------'   \ Mountain View, CA 94041 USA
Red Hat         `--' drepper at redhat.com `---------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE99k1n2ijCOnn/RHQRApZIAKCUN7C97J+NSjYYemzZ7gs1rouZkgCfUDSH
QIXJqjLP0LKt2pPs/J7lxwA=
=QgiF
-----END PGP SIGNATURE-----

      reply	other threads:[~2002-12-10 20:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-10 10:02 Jakub Jelinek
2002-12-10 12:23 ` Ulrich Drepper [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=3DF64D67.6070701@redhat.com \
    --to=drepper@redhat.com \
    --cc=jakub@redhat.com \
    --cc=libc-hacker@sources.redhat.com \
    --cc=roland@redhat.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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).