public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Ulrich Drepper <drepper@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:20:00 -0000	[thread overview]
Message-ID: <20020806081937.P20867@sunsite.ms.mff.cuni.cz> (raw)
In-Reply-To: <3D4EFF01.1080003@redhat.com>; from drepper@redhat.com on Mon, Aug 05, 2002 at 03:41:05PM -0700

On Mon, Aug 05, 2002 at 03:41:05PM -0700, Ulrich Drepper wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Roland McGrath wrote:
> 
> > Then we should make -O3 the default, should we not?
> 
> No.  See my mail to rth from Sunday or Saturday.
> 
> (There is a bug in gcc where it inlines far too much when -O3 is used.)

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).

Aren't we going to have a list of 10 or how many functions which need to
go through .plt and the rest does not? If yes,
then __attribute__ ((noinline)) for those 10 would suffice.

	Jakub

  reply	other threads:[~2002-08-06  6:20 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 [this message]
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

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=20020806081937.P20867@sunsite.ms.mff.cuni.cz \
    --to=jakub@redhat.com \
    --cc=drepper@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).