From: Paolo Carlini <pcarlini@unitus.it>
To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
Cc: gcc@gcc.gnu.org
Subject: Re: C++ aliasing changes on mainline (was: GCC 3.1 Prerelease)
Date: Wed, 24 Apr 2002 03:42:00 -0000 [thread overview]
Message-ID: <3CC68A27.9040007@unitus.it> (raw)
In-Reply-To: <Pine.BSF.4.44.0204232000250.2524-100000@pulcherrima.dbai.tuwien.ac.at>
Gerald Pfeifer wrote:
>I got mixed results. The binary with the changes above (and all CVS
>changes between Monday and Tuesday) was somewhat smaller than the
>original. Performance didn't change too much, either way.
>
Thank you very much Gerald.
Indeed, I find those numbers very interesting and very puzzling!
Definitely I did expect a clear positive effect of the C++ aliasing
patch... First, I have to learn more about the main features of such C++
code.
Ciao, Paolo.
next prev parent reply other threads:[~2002-04-24 10:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-23 10:46 GCC 3.1 Prerelease Paolo Carlini
2002-04-24 0:50 ` C++ aliasing changes on mainline (was: GCC 3.1 Prerelease) Gerald Pfeifer
2002-04-24 3:42 ` Paolo Carlini [this message]
2002-04-24 4:23 ` Jan Hubicka
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=3CC68A27.9040007@unitus.it \
--to=pcarlini@unitus.it \
--cc=gcc@gcc.gnu.org \
--cc=pfeifer@dbai.tuwien.ac.at \
/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).