From: Roland McGrath <roland@frob.com>
To: Ulrich Drepper <drepper@redhat.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:08:00 -0000 [thread overview]
Message-ID: <20020806070803.54E051BA1B@perdition.linnaean.org> (raw)
In-Reply-To: Ulrich Drepper's message of Mon, 5 August 2002 23:39:35 -0700 <3D4F6F27.1060405@redhat.com>
> 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.
I don't think it is so unreasonable. 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.
next prev parent reply other threads:[~2002-08-06 7:08 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 [this message]
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=20020806070803.54E051BA1B@perdition.linnaean.org \
--to=roland@frob.com \
--cc=drepper@redhat.com \
--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).