From: Roland McGrath <roland@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Andreas Jaeger <aj@suse.de>,
GNU libc hacker <libc-hacker@sources.redhat.com>
Subject: Re: problems with ctype...
Date: Wed, 18 Sep 2002 11:34:00 -0000 [thread overview]
Message-ID: <200209181834.g8IIY3k07883@magilla.sf.frob.com> (raw)
In-Reply-To: Jakub Jelinek's message of Monday, 16 September 2002 09:29:49 -0400 <20020916092949.A12870@devserv.devel.redhat.com>
> Nope, I mean -Wr. If libc.so doesn't have any R_386_GLOB_DAT __ctype_b
Ah, I see the problem now. Always forgetting about those pesky copy relocs.
I inserted compat_symbol (i.e. .symver) decls in lc-ctype.c where the
variables are set, and that gets those relocs bound early to the versioned
name and thus proper GLOB_DAT relocs in the shared object.
This exposed a trivial ld.so bug in handling relocs referring to
non-default versioned symbols defined in the same object, which I fixed.
I think this puts this problem to rest. The only thing I don't know is if
older binutils versions have any problem producing the right output with
this usage. I would tend to doubt off hand that it's a problem with the
new straightforward usage of the symbols by their versioned names.
next parent reply other threads:[~2002-09-18 18:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020916092949.A12870@devserv.devel.redhat.com>
2002-09-18 11:34 ` Roland McGrath [this message]
2002-09-15 20:55 Andreas Jaeger
2002-09-15 22:15 ` Roland McGrath
2002-09-15 23:52 ` Andreas Jaeger
2002-09-15 23:59 ` Roland McGrath
2002-09-16 0:01 ` Andreas Jaeger
2002-09-16 8:07 ` H. J. Lu
2002-09-16 21:54 ` Roland McGrath
2002-09-16 22:00 ` H. J. Lu
2002-09-16 0:01 ` Jakub Jelinek
2002-09-16 0:50 ` Andreas Jaeger
2002-09-16 2:22 ` Jakub Jelinek
2002-09-16 6:22 ` Roland McGrath
2002-09-16 8:04 ` H. J. Lu
2002-09-16 8:01 ` H. J. Lu
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=200209181834.g8IIY3k07883@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=aj@suse.de \
--cc=jakub@redhat.com \
--cc=libc-hacker@sources.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).