This is the mail archive of the 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]

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
>Originator:     Anthony Green
>Release:        3.3 20020908 (experimental)
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) 

	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.
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/
/tmp/ Invalid character `\uffff' in input.
1 error


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