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: Infinite loop in compiling javax/swing/text/html/parser/HTML_401F.list

From: Eric Botcazou <ebotcazou at libertysurf dot fr>
To: Dominique Dhumieres <dominiq at lps dot ens dot fr>
Cc: gcc at gcc dot gnu dot org, richard dot guenther at gmail dot com, ddaney at avtrex dot com
Date: Wed, 31 Oct 2007 20:11:02 +0100
Subject: Re: Infinite loop in compiling javax/swing/text/html/parser/HTML_401F.list
References: <20071027225815.E0F355BBA4@mailhost.lps.ens.fr> <84fc9c000710291129u1b4bf4bfv567b16de1ebcfb97@mail.gmail.com> <20071031134641.9D2FB5BBB3@mailhost.lps.ens.fr>

> Most of the improvement from my original post comes from
> gnu/javax/swing/text/html/parser/HTML_401F.deps, for which the compile time
> went from over 100 minutes to below 10 (twice due to multilib). For all the
> other pieces of code the saving (if any) was clearly well below a factor 2. 
> Does anyone understand what is so special to jc1 and HTML_401F in order to	
> explain this order of magnitude?

Very likely because HTML_401F relies heavily on memory partitioning, which is 
kind of a fuse that triggers when the number of virtual operands goes to the 
roof.  The fix for PR tree-optimization/33870 basically short-circuited it.

-- 
Eric Botcazou

References:
- Infinite loop in compiling javax/swing/text/html/parser/HTML_401F.list
  - From: Dominique Dhumieres
- Re: Infinite loop in compiling javax/swing/text/html/parser/HTML_401F.list
  - From: Richard Guenther
- Re: Infinite loop in compiling javax/swing/text/html/parser/HTML_401F.list
  - From: Dominique Dhumieres

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