Re: Infinitely long compilation

[Martin Kahlert <martin dot kahlert at infineon dot com>]

Hi Bryce,


On Thu, Mar 28, 2002 at 07:34:57PM +1200, Bryce McKinlay wrote:
> Martin Kahlert wrote:
> 
> >Looks very different to me.
> >
> >I look into it a bit deeper, now, seems to be something inside parse.y(do_resolve_class).
> >
> 
> Hmm, if this is a recent regression, can you try this fix for a bug in 
> my last patch, which I'm about to check in:
> 
> Index: parse.y
> ===================================================================
> RCS file: /cvs/gcc/egcs/gcc/java/parse.y,v
> retrieving revision 1.366
> diff -u -r1.366 parse.y
> --- parse.y     2002/03/28 04:28:22     1.366
> +++ parse.y     2002/03/28 07:33:51
> @@ -7034,7 +7034,8 @@
>  resolve_package (pkg, next, type_name)
>       tree pkg, *next, *type_name;
>  {
> -  tree current, decl;
> +  tree current;
> +  tree decl = NULL_TREE;
>    *type_name = NULL_TREE;
>  
>    /* The trick is to determine when the package name stops and were

Sorry, but the code in gcc-20020325 looks different:
  tree current, acc;
  tree type_name = NULL_TREE;
  const char *name = IDENTIFIER_POINTER (EXPR_WFL_NODE (pkg));

...

Perhaps your bug is younger than that.

Thanks anyway,
Martin.

PS: I do not have any clue, why the bug only shows on Solaris.

-- 
The early bird catches the worm. If you want something else for       
breakfast, get up later.