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: mainline "exploding"

From: cgd at broadcom dot com
To: zack at codesourcery dot com
Cc: "Jan Hubicka" <jh at suse dot cz>,"Gerald Pfeifer" <gerald at pfeifer dot com>,"Jan Hubicka" <hubicka at ucw dot cz>,gcc at gcc dot gnu dot org,rth at redhat dot com
Date: 16 Oct 2003 21:34:17 -0700
Subject: Re: mainline "exploding"
References: <Pine.BSF.4.58.0310140959170.50444@acrux.dbai.tuwien.ac.at><20031014083007.GB18393@atrey.karlin.mff.cuni.cz><Pine.BSF.4.58.0310141207520.33326@acrux.dbai.tuwien.ac.at><20031014120140.GG6212@kam.mff.cuni.cz><87k777py0p.fsf@egil.codesourcery.com><mailpost.1066150069.20382@news-sj1-1>

At Tue, 14 Oct 2003 16:47:50 +0000 (UTC), "Zack Weinberg" wrote:
> Jan Hubicka <jh@suse.cz> writes:
> 
> > 2) go ahead and enable unit-at-a-time by default for C++ at all levels
> 
> s/for C++// and I vote for this one.

Bug 12389 has the potential to cause lots of ICEs if turned on by
default, at least for ... a certain style of code.  (I don't
particularly like nested functions in C, but a lot of packages,
including glibc, seem fairly fond of them.)

(unit-at-a-time causes glibc to lose in other ways, too, on certain
platforms at least, but that's not unit-at-a-time's fault.  See
http://sources.redhat.com/ml/libc-alpha/2003-10/msg00013.html for
amusement.)

chris

Follow-Ups:
- Re: mainline "exploding"
  - From: Jan Hubicka

References:
- mainline "exploding"
  - From: Gerald Pfeifer
- Re: mainline "exploding"
  - From: Jan Hubicka
- Re: mainline "exploding"
  - From: Gerald Pfeifer
- Re: mainline "exploding"
  - From: Jan Hubicka
- Re: mainline "exploding"
  - From: Zack Weinberg

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