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: Tremendous increase in compile times for 3.4.1 with -mcpu=G5

From: Dale Johannesen <dalej at apple dot com>
To: David Edelsohn <dje at watson dot ibm dot com>
Cc: Matt Austern <austern at apple dot com>, Bradley Lucier <lucier at math dot purdue dot edu>, Dale Johannesen <dalej at apple dot com>, gcc at gcc dot gnu dot org
Date: Tue, 10 Aug 2004 20:52:16 -0700
Subject: Re: Tremendous increase in compile times for 3.4.1 with -mcpu=G5
References: <E6A45290-EB1B-11D8-8435-000A958F150A@math.purdue.edu> <44DA8981-EB1F-11D8-8435-000A958F150A@math.purdue.edu> <E0895594-EB20-11D8-8545-000A95AA5E5E@apple.com> <200408110152.i7B1qbD30882@makai.watson.ibm.com>

On Aug 10, 2004, at 6:52 PM, David Edelsohn wrote:

Matt Austern writes:

local alloc           : 117.49 (86%) usr   1.09 ( 8%) sys 221.13
(78%) wall

Matt> This is the culprit, of course.

	And most likely due to the mixed-mode 64-bit computation / 32-bit
ABI functionality enabled by default with -mcpu=G5

I suppose, but it's not obvious why that would cause local_alloc to do that much more work. Could we be tickling a bad algorithm in local-alloc?

Follow-Ups:
- Re: Tremendous increase in compile times for 3.4.1 with -mcpu=G5
  - From: Bradley Lucier

References:
- Tremendous increase in compile times for 3.4.1 with -mcpu=G5
  - From: Bradley Lucier
- Re: Tremendous increase in compile times for 3.4.1 with -mcpu=G5
  - From: Bradley Lucier
- Re: Tremendous increase in compile times for 3.4.1 with -mcpu=G5
  - From: Matt Austern
- Re: Tremendous increase in compile times for 3.4.1 with -mcpu=G5
  - From: David Edelsohn

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