This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
java/7950: jc1 parses files ending in 0x0d incorrectly
- From: green at redhat dot com
- To: gcc-gnats at gcc dot gnu dot org
- Date: Tue, 17 Sep 2002 07:05:46 -0700
- Subject: java/7950: jc1 parses files ending in 0x0d incorrectly
>Number: 7950
>Category: java
>Synopsis: jc1 parses files ending in 0x0d incorrectly
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: rejects-legal
>Submitter-Id: net
>Arrival-Date: Tue Sep 17 07:16:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: Anthony Green
>Release: 3.3 20020908 (experimental)
>Organization:
>Environment:
System: Linux dewey 2.4.7-10smp #1 SMP Thu Sep 6 17:09:31 EDT 2001 i686 unknown
Architecture: i686
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: /home/green/FSF/GCC/HEAD/gcc/configure --prefix=/es/scratch/green/FSF/i --enable-languages=c,c++,java --with-languages=c,c++,java --enable-threads : (reconfigured)
>Description:
I've come across some java source which emacs claims is a
"Mac" file (presumably edited on a Mac). In any case, it uses 0x0d as
the end-of-line character. gcj reports an error when this is the last
character in a source file.
>How-To-Repeat:
I will upload a test source file to the gnats page when it is created. But
you reall just need any source file which ends in 0x0d.
$ gcj -C /tmp/eofparse.java
/tmp/eofparse.java:4: Invalid character `\uffff' in input.
^
1 error
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: