From: Ulrich Drepper <drepper@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Roland McGrath <roland@frob.com>,
Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: [PATCH] Nuke another 21 .plt slots
Date: Mon, 05 Aug 2002 23:43:00 -0000 [thread overview]
Message-ID: <3D4F6F27.1060405@redhat.com> (raw)
In-Reply-To: <20020806081937.P20867@sunsite.ms.mff.cuni.cz>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jakub Jelinek wrote:
> If -O3 could inline only static or explicit inline routines, it would
> be far less useful than it currently is (for the applications which benefit
> from automatic inlining, of course, the majority does not).
The problem is not loss of optimization. The semantics f code gets
changed. And incorrectly so. gcc cannot inline a non-static function
unless its visibility != default. It might be possible to add a gcc
option to signal that all functions can be assumed to be non-preemptible.
- --
- ---------------. ,-. 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
iD8DBQE9T28s2ijCOnn/RHQRAvVsAJ0T3Y7mxqpqNxVndZWjPCZ+hkrSXQCeP9AK
18XrDpDvZ8qqVTAew4Y1cSs=
=7nCZ
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2002-08-06 6:43 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 [this message]
2002-08-06 0:08 ` Roland McGrath
2002-08-06 0:10 ` Roland McGrath
2002-08-06 0:19 ` Ulrich Drepper
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=3D4F6F27.1060405@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).