This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [Patch, libjava] use -fnon-call-exceptions rather than -fasynchronous-unwind-tables.

From: Mike Stump <mikestump at comcast dot net>
To: Jakub Jelinek <jakub at redhat dot com>
Cc: Richard Guenther <richard dot guenther at gmail dot com>, IainS <developer at sandoe-acoustics dot co dot uk>, java-patches at gcc dot gnu dot org, gcc patches <gcc-patches at gcc dot gnu dot org>, Richard Henderson <rth at redhat dot com>
Date: Wed, 18 Aug 2010 09:34:16 -0700
Subject: Re: [Patch, libjava] use -fnon-call-exceptions rather than -fasynchronous-unwind-tables.
References: <6533D5F3-D5AE-475F-A309-625BC7ACBF48@sandoe-acoustics.co.uk> <AANLkTikfSr-E-RE08TUxeFT2bQbDXiwUOX4cdOcVoS1q@mail.gmail.com> <20100818094527.GN702@tyan-ft48-01.lab.bos.redhat.com>

On Aug 18, 2010, at 2:45 AM, Jakub Jelinek wrote:
> Yeah, I think -fa-u-t is right, otherwise you can't backtrace through
> signal handlers.  If Darwin unwinder is lame enough that it can't grok it,
> let it change just on Darwin and don't punish sane OSes.

Walking the darwin signal handers works just fine...  I can't recall exactly how well the async signals work v the sync signals.

References:
- [Patch, libjava] use -fnon-call-exceptions rather than -fasynchronous-unwind-tables.
  - From: IainS
- Re: [Patch, libjava] use -fnon-call-exceptions rather than -fasynchronous-unwind-tables.
  - From: Richard Guenther
- Re: [Patch, libjava] use -fnon-call-exceptions rather than -fasynchronous-unwind-tables.
  - From: Jakub Jelinek

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]