public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: apbianco@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: java/5810: unrecognized character in input stream
Date: Fri, 01 Mar 2002 22:56:00 -0000 [thread overview]
Message-ID: <20020302065601.25756.qmail@sources.redhat.com> (raw)
The following reply was made to PR java/5810; it has been noted by GNATS.
From: Tom Tromey <tromey@redhat.com>
To: bender@ugcs.caltech.edu
Cc: gcc-gnats@gcc.gnu.org, Alexandre Petit-Bianco <apbianco@redhat.com>
Subject: Re: java/5810: unrecognized character in input stream
Date: 02 Mar 2002 00:14:06 -0700
>>>>> ">" == bender <bender@ugcs.caltech.edu> writes:
Hey. I went to Tech. Ricketts, class of 90.
>> GCJ has trouble with extended ascii characters in variable
>> identifiers. Sun's JDK happily accepts the following testcase.
>> To repeat, type: gcj a.java -o a --main=a -static
By default gcj tries to use your locale's encoding as the encoding for
its input files. Perhaps this isn't working on your platform for some
reason (some versions of Solaris have problems in this area).
You can always override, e.g.:
gcj --encoding=ISO-8859-1 ...
The names of the encodings are system-dependent, except that `UTF-8'
will work anywhere (won't help in your case, as your file is Latin-1).
This is all mentioned in the manual.
I'm a bit surprised you didn't get an error from gcj explaining the
situation. Alex, was that error in 3.0? Or is it new with 3.1?
I can never remember these things.
Tom
next reply other threads:[~2002-03-02 6:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-01 22:56 Tom Tromey [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-21 11:09 bangerth
2002-03-01 20:43 apbianco
2002-03-01 20:36 bender
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020302065601.25756.qmail@sources.redhat.com \
--to=tromey@redhat.com \
--cc=apbianco@gcc.gnu.org \
--cc=gcc-prs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).