public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: Roger Sayle <roger@eyesopen.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Compilation-time suggestion
Date: Mon, 19 Jan 2004 17:58:00 -0000	[thread overview]
Message-ID: <m33cab6d35.fsf@uniton.integrable-solutions.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0401190934380.23549-100000@www.eyesopen.com>

Roger Sayle <roger@eyesopen.com> writes:

| I have a proposal/suggestion for perhaps improving GCC compilation
| time: Perhaps we could make more use of __builtin_expect inside the
| compiler itself.

This has been suggested in the past

  http://gcc.gnu.org/ml/libstdc++/2002-11/msg00151.html

and RTH made this comment:

  http://gcc.gnu.org/ml/libstdc++/2002-11/msg00171.html

In fact, from a recent thread on libstdc++ list, I've come to agree
with RTH comment. 

I believe you would benefit much more from *algorithmic* and
*data-structure* improvements than from __builtin_expect which would
just add one more level of obfuscation to the already difficult to
follow source base.  Let's go that way first.

-- Gaby

      reply	other threads:[~2004-01-19 17:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-19 17:46 Roger Sayle
2004-01-19 17:58 ` Gabriel Dos Reis [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=m33cab6d35.fsf@uniton.integrable-solutions.net \
    --to=gdr@integrable-solutions.net \
    --cc=gcc@gcc.gnu.org \
    --cc=roger@eyesopen.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).