public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: tromey@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: java/5986: SIGSEGV in __gcj_personality_v0
Date: Wed, 27 Mar 2002 15:06:00 -0000	[thread overview]
Message-ID: <20020327230602.20125.qmail@sources.redhat.com> (raw)

The following reply was made to PR java/5986; it has been noted by GNATS.

From: Tom Tromey <tromey@redhat.com>
To: Jeff Sturm <jsturm@one-point.com>
Cc: gcc-gnats@gcc.gnu.org, Alexandre Petit-Bianco <apbianco@redhat.com>
Subject: Re: java/5986: SIGSEGV in __gcj_personality_v0
Date: 27 Mar 2002 16:39:29 -0700

 Jeff> Try this one.
 
 This patch fixes the problem for me.  I think the comment explains
 what is going on; if you think of a way to improve it let me know.
 
 I've only tested this minimally.  Could you try it on your code?
 
 Alex, as always, I desire your input.
 
 Tom
 
 Index: ChangeLog
 from  Tom Tromey  <tromey@redhat.com>
 
 	* except.c (expand_end_java_handler): If the handler type is NULL,
 	use java.lang.Throwable.  Fixes PR java/5986.
 
 Index: except.c
 ===================================================================
 RCS file: /cvs/gcc/gcc/gcc/java/except.c,v
 retrieving revision 1.26
 diff -u -r1.26 except.c
 --- except.c 2001/03/28 11:01:47 1.26
 +++ except.c 2002/03/27 23:03:07
 @@ -1,5 +1,5 @@
  /* Handle exceptions for GNU compiler for the Java(TM) language.
 -   Copyright (C) 1997, 1998, 1999, 2000 Free Software Foundation, Inc.
 +   Copyright (C) 1997, 1998, 1999, 2000, 2002 Free Software Foundation, Inc.
  
  This file is part of GNU CC.
  
 @@ -372,7 +372,17 @@
    expand_start_all_catch ();
    for ( ; handler != NULL_TREE; handler = TREE_CHAIN (handler))
      {
 -      expand_start_catch (TREE_PURPOSE (handler));
 +      /* For bytecode we treat exceptions a little unusually.  A
 +	 `finally' clause looks like an ordinary exception handler for
 +	 Throwable.  The reason for this is that the bytecode has
 +	 already expanded the finally logic, and we would have to do
 +	 extra (and difficult) work to get this to look like a
 +	 gcc-style finally clause.  */
 +      tree type = TREE_PURPOSE (handler);
 +      if (type == NULL)
 +	type = throwable_type_node;
 +
 +      expand_start_catch (type);
        expand_goto (TREE_VALUE (handler));
        expand_end_catch ();
      }


             reply	other threads:[~2002-03-27 23:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-27 15:06 Tom Tromey [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-28 17:26 Jeff Sturm
2002-03-28 16:46 Tom Tromey
2002-03-28 16:41 tromey
2002-03-28 14:56 Alexandre Petit-Bianco
2002-03-28 14:06 Jeff Sturm
2002-03-27 16:56 Tom Tromey
2002-03-27 16:36 Alexandre Petit-Bianco
2002-03-27 15:05 tromey
2002-03-27 13:26 Tom Tromey
2002-03-21  6:46 Jeff Sturm
2002-03-21  1:26 Bryce McKinlay
2002-03-20 17:26 Jeff Sturm
2002-03-20 15:46 Tom Tromey
2002-03-17  7:16 jsturm

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=20020327230602.20125.qmail@sources.redhat.com \
    --to=tromey@redhat.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=tromey@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).