From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19862 invoked by alias); 29 Mar 2002 01:26:01 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 19829 invoked by uid 71); 29 Mar 2002 01:26:00 -0000 Date: Thu, 28 Mar 2002 17:26:00 -0000 Message-ID: <20020329012600.19828.qmail@sources.redhat.com> To: tromey@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Jeff Sturm Subject: Re: java/5986: SIGSEGV in __gcj_personality_v0 Reply-To: Jeff Sturm X-SW-Source: 2002-03/txt/msg01123.txt.bz2 List-Id: The following reply was made to PR java/5986; it has been noted by GNATS. From: Jeff Sturm To: Tom Tromey Cc: gcc-gnats@gcc.gnu.org Subject: Re: java/5986: SIGSEGV in __gcj_personality_v0 Date: Thu, 28 Mar 2002 20:16:15 -0500 (EST) On 28 Mar 2002, Tom Tromey wrote: > Jeff> (Well, I had to use javac, since "gcj -C" caused verifier > Jeff> errors... but's that's another problem.) > > Verifier errors from gcj itself? Yes. > Unfortunately there are some known `gcj -C' bugs. They're in Gnats. I figured that. I really should find out whether this is a new problem. > I'm curious why you're compiling to bytecode first. Sometimes I don't (and couldn't until you fixed this PR). Two reasons mainly: - I don't always have source - Compiling jars is incredibly convenient, I can do things like gcj -shared -O2 -fPIC -fjni /opt/oracle/jdbc/lib/classes111.zip \ -o liborajdbc.so I haven't yet reworked our entire build process for gcj. Someday maybe I'll autoconfiscate. Jeff