Re: libgcj/5846: gcj compile fails on comments-only file

[Andrew Pinski <pinskia at physics dot uc dot edu>]

The following reply was made to PR libgcj/5846; it has been noted by GNATS.

From: Andrew Pinski <pinskia@physics.uc.edu>
To: hin@alma.com
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: libgcj/5846: gcj compile fails on comments-only file
Date: Tue, 5 Mar 2002 16:22:03 -0500

 This is fixed in at least in 3.2 (20020302) and also the 3.1 right 
 before the branch.
 
 Thanks,
 Andrew Pinski
 
 On Tuesday, March 5, 2002, at 04:08 , hin@alma.com wrote:
 
 >
 >> Number:         5846
 >> Category:       libgcj
 >> Synopsis:       gcj compile fails on comments-only file
 >> Confidential:   no
 >> Severity:       non-critical
 >> Priority:       medium
 >> Responsible:    unassigned
 >> State:          open
 >> Class:          rejects-legal
 >> Submitter-Id:   net
 >> Arrival-Date:   Tue Mar 05 13:16:00 PST 2002
 >> Closed-Date:
 >> Last-Modified:
 >> Originator:     John K. Hinsdale
 >> Release:        3.0.4
 >> Organization:
 > Alma Mater Software, Inc.
 >> Environment:
 > System: Linux van-halen 2.4.10 #1 Mon Dec 24 07:29:46 EST 2001 i686 
 > unknown
 > Architecture: i686
 > host: i686-pc-linux-gnu
 > build: i686-pc-linux-gnu
 > target: i686-pc-linux-gnu
 > configured with: ./configure
 >> Description:
 > 	When compiling a Java source file that consists only of comments,
 > 	gcj gets a segmentation fault.
 >> How-To-Repeat:
 > 	Make a java source file with one or more lines of comments:
 > 		// This is a comment in myfile.java
 > 		/* This is also
 > 			a comment */
 > 	When you compile it, e.g.,:
 > 		gcj -c -g myfile.java
 > 	gcj will seg fault.
 >> Fix:
 > 	Workaround:
 > 	Don't include the file in one's compilation.  However, a big
 > 	system might want to be configured in such a away
 > 	that results in source files ending up having all
 > 	comments.  It's convenient at times to comment out an
 > 	entire file when developing.
 >> Release-Note:
 >> Audit-Trail:
 >> Unformatted:
 >
 >