c++/9983: Internal compiler error

smanagoli@projects.sdsu.edu smanagoli@projects.sdsu.edu
Fri Mar 14 20:06:00 GMT 2003


The following reply was made to PR c++/9983; it has been noted by GNATS.

From: smanagoli@projects.sdsu.edu
To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
   nobody@gcc.gnu.org, sameermanagoli@yahoo.com, smanagoli@projects.sdsu.edu,
   gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: c++/9983: Internal compiler error
Date: Fri, 14 Mar 2003 14:56:16 -0500

 Dear Dir,
 
 PLease let me know the detailed solution of the
 problem.I'm getting stuck at the same point.
 
 Thanks,
 Sameer
 
 ----- Original Message -----
 From: bangerth@dealii.org
 Date: Tuesday, March 11, 2003 5:00 pm
 Subject: Re: c++/9983: Internal compiler error
 
 > Synopsis: Internal compiler error
 > 
 > State-Changed-From-To: feedback->closed
 > State-Changed-By: bangerth
 > State-Changed-When: Tue Mar 11 22:00:16 2003
 > State-Changed-Why:
 >    Reproduced with 3.2, but already fixed with 3.2.2.
 >    
 >    Sameer, for next time you file a bug report: if
 you get
 >    an internal compiler error and it tells you a
 www address,
 >    and later on I send you the same address twice
 more, it 
 >    would be helpful if you could take a look at
 it. It reads
 >    that what we need are the _preprocessed_
 source, and also 
 >    that you can generate these with the
 -save-temps flags.
 >    We don't want to have one file (as in the first
 report),
 >    two files (what you sent me the second time),
 and we don't
 >    want to have whole tar archives (as what I got
 the third
 >    time). I was lucky that I could reproduce your
 problem
 >    from these, but you could have saves us all
 some time if
 >    you would have followed the instructions on
 that page.
 >    
 >    Thanks anyway
 >      Wolfgang
 > 
 >
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-
 > trail&database=gcc&pr=9983
 



More information about the Gcc-prs mailing list