This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: [patch] Re: Another weird sparc solaris 2.8 compiler error
- To: tromey at redhat dot com
- Subject: Re: [patch] Re: Another weird sparc solaris 2.8 compiler error
- From: Alexandre Petit-Bianco <apbianco at cygnus dot com>
- Date: Thu, 1 Feb 2001 15:29:30 -0800 (PST)
- Cc: Bryce McKinlay <bryce at albatross dot co dot nz>, Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>, Edgar Villanueva <EVillanueva at dynamicsoft dot com>, java at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
- References: <Pine.BSF.4.32.0102010157480.96364-100000@deneb.dbai.tuwien.ac.at><3A790CDB.BA8DC4C6@albatross.co.nz><87zog6gfe4.fsf@creche.redhat.com>
- Reply-To: apbianco at cygnus dot com
Tom Tromey writes:
> Does anybody know why we had an error() function here in the first
> place?
It not something that we've been using recently, or even ever. Maybe
it was satisfying a symbol while linking along with some other .os
from gcc. Oh, I see: we used to link jvgenmain against mangle.o, and
mangle.o always used `error.' We don't anymore because I couldn't get
it quickly to work when I was working on the new mangling scheme. Now,
maybe it was a bit short sighted from me to do that, especially with
the UTF8-in-mangled-name-if-supported that we'll put in shortly, plus
the fact that we aren't able to generate `main' for a class bearing
unicodes in its name anymore :-(
I'll put that on my todo list.
./A