public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jan Hubicka <hubicka@ucw.cz>
To: Andrew Haley <aph@redhat.com>
Cc: Jan Hubicka <hubicka@ucw.cz>, gcc@gcc.gnu.org, java@gcc.gnu.org
Subject: Re: GCC EH unwinding bug and libjava calling std::terminate ()
Date: Fri, 27 Mar 2009 18:14:00 -0000	[thread overview]
Message-ID: <20090327181436.GB32205@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <49CCD05D.7040707@redhat.com>

> Jan Hubicka wrote:
> 
> > current mainline is buggy in EH unwinding effectivly ignoring
> > MUST_NOT_THROW regions when reached via RESX from local handlers.
> > See http://gcc.gnu.org/ml/gcc-patches/2009-03/msg01285.html for details.
> > 
> > Unfortunately this patch causes bootstrap failure when building libjava,
> > because std::terminate() is now called.  The call comes from
> > run_proxy in natVMProxy.cc where we have cleanup code calling
> > destructor of:
> > 
> > _Jv_InterpFrame frame_desc (self->self, thread, proxyClass,
> >                               NULL, frame_proxy);
> > 
> > Now the desctuctor is pretty simple but because of:
> > 'if a destructor called during stack unwinding exits with an exception,
> > std::terminate is called'
> > 
> > and because we use -fnon-call-excpetion and destructor is accessing
> > memory, we keep MUST_NOT_THROW terminate () call accessible
> > because after inlining the destructor, cleanup might unwind up
> > to that MUST_NOT_THROW.
> > 
> > Questio is how to fix this situation? Shall we link with C++ runtime,
> 
> Please don't.
> 
> > or use -fno-non-call-exceptions
> 
> No, because it might segfault, and we need to catch it.
> 
> > to build this file or somehow restruture
> > code to avoid this case?
> 
> /* Gimplify a MUST_NOT_THROW_EXPR.  */
> 
> static enum gimplify_status
> gimplify_must_not_throw_expr (tree *expr_p, gimple_seq *pre_p)
> {
>   tree stmt = *expr_p;
>   tree temp = voidify_wrapper_expr (stmt, NULL);
>   tree body = TREE_OPERAND (stmt, 0);
>   tree termination;
> 
>   if (pragma_java_exceptions)
>     termination = terminate_node;
>   else
>     termination = abort_node;

OK, pragma_java_exceptions variable is not there, does something like
this work for you?

I would like to commit this to mainline so the MUST_NOT_THROW fix can go
as well.  I am commiting it to pretty-ipa in meantime.

Honza

Index: cp/except.c
===================================================================
*** cp/except.c	(revision 145101)
--- cp/except.c	(working copy)
*************** choose_personality_routine (enum languag
*** 353,358 ****
--- 353,359 ----
  
      case lang_java:
        state = chose_java;
+       terminate_node = built_in_decls [BUILT_IN_ABORT];
        eh_personality_libfunc = init_one_libfunc (USING_SJLJ_EXCEPTIONS
  						 ? "__gcj_personality_sj0"
  						 : "__gcj_personality_v0");

  reply	other threads:[~2009-03-27 18:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-27 12:38 Jan Hubicka
2009-03-27 13:11 ` Andrew Haley
2009-03-27 18:14   ` Jan Hubicka [this message]
2009-03-27 18:21     ` Andrew Haley
2009-03-27 18:25       ` Jan Hubicka

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=20090327181436.GB32205@atrey.karlin.mff.cuni.cz \
    --to=hubicka@ucw.cz \
    --cc=aph@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=java@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).