This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: GCC 3.3 compile speed regression - AN ANSWER

From: Gianni Mariani <gmariani at chaincast dot com>
To: Linus Torvalds <torvalds at transmeta dot com>
Cc: Matt Austern <austern at apple dot com>, jsm28 at cam dot ac dot uk, gcc at gcc dot gnu dot org
Date: Tue, 11 Feb 2003 23:14:37 -0800
Subject: Re: GCC 3.3 compile speed regression - AN ANSWER
Organization: Chaincast, Inc
References: <Pine.LNX.4.44.0302112156540.4571-100000@home.transmeta.com>
Reply-to: gmariani at chaincast dot com

Linus Torvalds wrote:

I'm guessing here, but I'd not be surprised if a few-hundred-line GUI C++
file would tend to easily explode to a hundred _thousand_ lines with
include files fully expanded. The front end is involved with all of them,
while the back-end is really only involved with the original few hundred
lines and some code expansion from inlining and macros.

Linus, you're reaching here ! This is not a C++ issue as much as it it a software design / development issue.

The exact same things can be said for C.

I aslo doubt that the incremental syntactic complexity of C++ over would contribute significantly towards
the compilation time. These again would be mainly design factors.

Let's face it, performance of the compiler is nowhere near as significant as a kernel and the design trade
off between efficiency/performance and ease of development are different.

References:
- Re: GCC 3.3 compile speed regression - AN ANSWER
  - From: Linus Torvalds

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]