From: Ulrich Drepper <drepper@redhat.com>
To: Roland McGrath <roland@frob.com>
Cc: Jakub Jelinek <jakub@redhat.com>,
Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: [PATCH] Nuke another 21 .plt slots
Date: Tue, 06 Aug 2002 00:19:00 -0000 [thread overview]
Message-ID: <3D4F7775.3070904@redhat.com> (raw)
In-Reply-To: <20020806070803.54E051BA1B@perdition.linnaean.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Roland McGrath wrote:
> I don't think it is so unreasonable.
What exactly? That gcc by default is generating code with different
semantics based on the optimization level?
> Anything that is written so that it
> would work with static linking would work will come out right (i.e. you can
> only inline in the same module and it would be a multiple definition if
> there were a competing definition elsewhere), except for special cases
> defining weak functions.
I have no problem with this being possible. But the user must tell the
compiler to do so. There is a lot of code out there which depends on
interposition being possible. All optimizations default on the safe
side, why not this one as well?
- --
- ---------------. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
Red Hat `--' drepper at redhat.com `------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE9T3d62ijCOnn/RHQRAsxlAKChbETqVF7MiHubYxzSugqU8nJ8RACeIunj
3no+m3gkdxDOKdinWmUQYks=
=xmoz
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2002-08-06 7:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-05 14:54 Jakub Jelinek
2002-08-05 15:11 ` Roland McGrath
2002-08-05 15:18 ` Jakub Jelinek
2002-08-05 15:21 ` Roland McGrath
2002-08-05 15:42 ` Ulrich Drepper
2002-08-05 23:20 ` Jakub Jelinek
2002-08-05 23:43 ` Ulrich Drepper
2002-08-06 0:08 ` Roland McGrath
2002-08-06 0:10 ` Roland McGrath
2002-08-06 0:19 ` 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=3D4F7775.3070904@redhat.com \
--to=drepper@redhat.com \
--cc=jakub@redhat.com \
--cc=libc-hacker@sources.redhat.com \
--cc=roland@frob.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).