From: Bryce McKinlay <bmckinlay@gmail.com>
To: Jack Howarth <howarth@bromo.med.uc.edu>
Cc: Eric Botcazou <ebotcazou@adacore.com>, java@gcc.gnu.org
Subject: Re: [patch] Fix oddity in personality routine
Date: Sun, 15 Nov 2009 23:02:00 -0000 [thread overview]
Message-ID: <7230133d0911151501k19f447a8of7956ebe1cea8813@mail.gmail.com> (raw)
In-Reply-To: <20091113191758.GA22781@bromo.med.uc.edu>
On Fri, Nov 13, 2009 at 7:17 PM, Jack Howarth <howarth@bromo.med.uc.edu> wrote:
>> Index: exception.cc
>> ===================================================================
>> --- exception.cc (revision 154059)
>> +++ exception.cc (working copy)
>> @@ -328,7 +328,7 @@ PERSONALITY_FUNCTION (int version,
>> #ifdef HAVE_GETIPINFO
>> ip = _Unwind_GetIPInfo (context, &ip_before_insn);
>> #else
>> - ip = _Unwind_GetIP (context) - 1;
>> + ip = _Unwind_GetIP (context);
>> #endif
>> if (! ip_before_insn)
>> --ip;
>
>
> Shouldn't this fix also get backported to gcc-4_4-branch and
> gcc-4_3-branch as well? They both have r128098.
Jack, can you confirm that this actually fixes the problem you are
seeing on Darwin? r128098 dates from 2007 - it's hard to believe that
nobody has had a working GCJ on Darwin since then!
Bryce
next prev parent reply other threads:[~2009-11-15 23:02 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-13 17:49 Eric Botcazou
2009-11-13 17:57 ` Andrew Haley
2009-11-13 18:36 ` Jack Howarth
2009-11-13 18:39 ` Andrew Haley
2009-11-13 19:18 ` Jack Howarth
2009-11-15 23:02 ` Bryce McKinlay [this message]
2009-11-16 14:22 ` Jack Howarth
2009-11-16 15:12 ` Jack Howarth
2009-11-16 15:17 ` Andrew Haley
2009-11-16 15:34 ` Jack Howarth
2009-11-16 16:59 ` Andrew Haley
2009-11-16 18:07 ` Jack Howarth
2009-11-16 19:10 ` Andrew Haley
2009-11-16 19:48 ` Jack Howarth
2009-11-17 0:48 ` Jack Howarth
2009-11-17 10:59 ` Andrew Haley
2009-11-17 14:05 ` Jack Howarth
2009-11-17 14:56 ` Andrew Haley
2009-11-17 16:18 ` Jack Howarth
2009-11-17 16:22 ` Andrew Haley
2009-11-17 17:07 ` Jack Howarth
2009-11-17 17:14 ` Andrew Haley
2009-11-17 17:38 ` Jack Howarth
2009-11-27 10:37 ` borlum
2009-11-27 10:40 ` Andrew Haley
2009-11-27 10:52 ` borlum
2009-11-27 14:20 ` Bryce McKinlay
2009-11-27 16:29 ` Jack Howarth
2009-11-27 21:51 ` Jack Howarth
2009-11-28 10:43 ` Andrew Haley
2009-11-29 17:48 ` Jack Howarth
2009-11-29 18:01 ` Andrew Haley
2009-11-29 18:48 ` Jack Howarth
2009-11-30 10:09 ` Andrew Haley
2009-11-30 16:01 ` Jack Howarth
2009-11-30 16:07 ` Andrew Haley
2009-12-01 5:02 ` Jack Howarth
2009-12-01 9:30 ` Andrew Haley
2009-12-01 17:04 ` Jack Howarth
2009-12-01 17:24 ` Andrew Haley
2009-12-01 23:29 ` Jack Howarth
2009-12-02 9:34 ` Andrew Haley
2009-12-03 1:08 ` Jack Howarth
2009-12-03 10:26 ` Andrew Haley
2009-12-03 14:03 ` Jack Howarth
2009-12-03 14:10 ` Andrew Haley
2009-12-03 19:18 ` Boehm, Hans
2009-12-03 21:25 ` Andrew Haley
2009-12-04 3:01 ` Jack Howarth
2009-12-04 9:45 ` Andrew Haley
2009-12-04 4:12 ` Jack Howarth
2009-12-04 9:44 ` Andrew Haley
2009-12-04 14:51 ` Jack Howarth
2009-12-04 14:59 ` Andrew Haley
2009-12-04 15:23 ` Jack Howarth
2009-12-04 15:48 ` Andrew Haley
2009-12-04 15:57 ` Bryce McKinlay
2009-12-05 4:37 ` Jack Howarth
2009-12-05 6:54 ` Jack Howarth
2009-12-04 15:59 ` Jack Howarth
2009-12-04 16:06 ` Andrew Haley
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=7230133d0911151501k19f447a8of7956ebe1cea8813@mail.gmail.com \
--to=bmckinlay@gmail.com \
--cc=ebotcazou@adacore.com \
--cc=howarth@bromo.med.uc.edu \
--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).