public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joe Buck <jbuck@synopsys.COM>
To: gdr@codesourcery.com (Gabriel Dos Reis)
Cc: jbuck@synopsys.com (Joe Buck),
	pfeifer@dbai.tuwien.ac dot@(Gerald Pfeifer),
	mark@codesourcery.com (Mark Mitchell),
	gcc@gcc.gnu.org (gcc@gcc.gnu.org)
Subject: Re: C++ compile-time regressions (was: GCC 3.0.1 Status Report)
Date: Tue, 24 Jul 2001 10:44:00 -0000	[thread overview]
Message-ID: <200107241743.KAA08441@atrus.synopsys.com> (raw)
In-Reply-To: <flwv4yb5yu.fsf@sel.cmla.ens-cachan.fr>

> Joe Buck <jbuck@synopsys.COM> writes:
> 
> | > I'm rather sure, though, that g++ is not generating efficient code for
> | > complicated, nested STL and STL-like structures in the presence of
> | > libstdc++-v3 (iterators are now classes instead of pointers).
> | 
> | But the classes have one member, so we should still be getting equivalent
> | code, provided that we get ADDRESSOF working as well as it did in 2.95.x.
> 
> Now that we have a branch for doing tree-based optimization, what do
> you think about trying to implement "scalar replacement of aggregates"
> optimization and see how good we can do with STL-like structures?

Yes!  This is very important, not just for STL-like structures, but for
proxy objects (e.g. references to bits in a packed bit vector class).

You'll find some good test cases in Boost, particularly the Boost Graph
Library; our current compilers (2.95.x or 3.0.x) do poorly because many
of the iterators and function results are classes with more than one data
member.


  reply	other threads:[~2001-07-24 10:44 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-18 18:41 GCC 3.0.1 Status Report Mark Mitchell
2001-07-19  6:17 ` Joseph S. Myers
2001-07-20  3:45 ` Nathan Sidwell
2001-07-20 10:26 ` C++ compile-time regressions (was: GCC 3.0.1 Status Report) Gerald Pfeifer
2001-07-20 10:54   ` Nathan Sidwell
2001-07-20 16:41     ` Loren James Rittle
2001-07-23  5:17       ` Gerald Pfeifer
2001-07-23 11:56       ` Daniel Berlin
2001-07-23  2:51     ` Gerald Pfeifer
2001-07-20 10:55   ` Mark Mitchell
2001-07-20 14:22     ` Joe Buck
2001-07-20 16:28       ` Mark Mitchell
2001-07-20 21:05         ` Joe Buck
2001-07-23 10:44           ` Gerald Pfeifer
2001-07-23 11:12             ` Joe Buck
2001-07-23 11:57               ` Gerald Pfeifer
2001-07-23 13:30                 ` Joe Buck
2001-07-24  7:18                   ` Gerald Pfeifer
2001-07-24  7:55                     ` Daniel Berlin
2001-07-24 10:09                     ` Joe Buck
2001-07-24 10:19                       ` Gabriel Dos Reis
2001-07-24 10:44                         ` Joe Buck [this message]
2001-07-24 10:56                           ` Gabriel Dos Reis
2001-07-24 10:25                       ` Daniel Berlin
2001-07-24 10:49                         ` Joe Buck
2001-07-24 11:08                           ` Daniel Berlin
2001-07-23 14:36                 ` Mark Mitchell
2001-07-25  8:06                   ` Gerald Pfeifer
2001-08-02  0:20                     ` C++ compile-time regressions Gerald Pfeifer
2001-08-02  0:26                       ` Mark Mitchell
2001-08-02 11:00                       ` aoliva
2001-08-02 12:00                         ` Mark Mitchell
2001-08-02 12:26                           ` aoliva
2001-08-02 12:37                             ` Joe Buck
2001-08-02 12:41                             ` Mark Mitchell
2001-08-02 12:48                               ` Joe Buck
2001-08-02 13:53                       ` Daniel Berlin
2001-08-07  7:54                         ` Gerald Pfeifer
2001-07-23 11:54             ` C++ compile-time regressions (was: GCC 3.0.1 Status Report) Daniel Berlin
2001-07-23 12:42               ` Bernd Schmidt
2001-07-23 12:50               ` law
2001-07-23 13:15                 ` Daniel Berlin
2001-07-23 14:00                   ` law
2001-07-20 10:57   ` Daniel Berlin
2001-07-20 14:20   ` Joe Buck
2001-07-25 17:52 ` GCC 3.0.1 Status Report Marc Espie
2001-08-13 23:15   ` Mark Mitchell

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=200107241743.KAA08441@atrus.synopsys.com \
    --to=jbuck@synopsys.com \
    --cc=gdr@codesourcery.com \
    --cc=pfeifer@dbai.tuwien.ac \
    /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).