From: Dan Kegel <dank@kegel.com>
To: GCC Mailing List <gcc@gcc.gnu.org>
Subject: Re: compiler memory use optimization
Date: Sun, 21 Nov 2004 06:49:00 -0000 [thread overview]
Message-ID: <419FD23A.7070204@kegel.com> (raw)
Joe Buck wrote:
> 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.
The scars on my back say large C++ applications by even very
good programmers can be a lot of work to port from gcc-3.3 to gcc-3.4.
Or from gcc-2.95.3 to gcc-3.3. Or from 32 bit to 64 bit. Or from
gcc-3.4 to icc-8.1. Any big change brings its own set of problems...
- Dan
--
Trying to get a job as a c++ developer? See http://kegel.com/academy/getting-hired.html
next reply other threads:[~2004-11-21 0:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-21 6:49 Dan Kegel [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-18 18:45 naje
2004-11-18 19:33 ` Giovanni Bajo
2004-11-18 22:30 ` Joe Buck
2004-11-18 22:45 ` Mike Stump
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=419FD23A.7070204@kegel.com \
--to=dank@kegel.com \
--cc=gcc@gcc.gnu.org \
/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).