From: Joe Buck <Joe.Buck@synopsys.COM>
To: Giovanni Bajo <rasky@develer.com>
Cc: naje <najeiv@ukr.net>, gcc@gcc.gnu.org
Subject: Re: compiler memory use optimization
Date: Thu, 18 Nov 2004 22:30:00 -0000 [thread overview]
Message-ID: <20041118113323.A11981@synopsys.com> (raw)
In-Reply-To: <0e5401c4cd9e$bf2bc4a0$f503030a@mimas>; from rasky@develer.com on Thu, Nov 18, 2004 at 07:45:16PM +0100
On Thu, Nov 18, 2004 at 07:45:16PM +0100, Giovanni Bajo wrote:
> The good news is that 3.4 is much better [than 3.3] on many testcases.
> (Un)luckily, it is also much more ISO/ANSI C++ standard compliant, so
> upgrading from 3.3 to 3.4 for a large C++ applications could be non-trivial.
This is mainly the case for those who have never used compilers other than
g++, and who learn the language by throwing code at the compiler and
seeing what works.
next prev parent reply other threads:[~2004-11-18 19:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-18 18:45 naje
2004-11-18 19:33 ` Giovanni Bajo
2004-11-18 22:30 ` Joe Buck [this message]
2004-11-18 22:45 ` Mike Stump
2004-11-21 6:49 Dan Kegel
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=20041118113323.A11981@synopsys.com \
--to=joe.buck@synopsys.com \
--cc=gcc@gcc.gnu.org \
--cc=najeiv@ukr.net \
--cc=rasky@develer.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).