From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32127 invoked by alias); 14 Sep 2013 15:47:11 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 32074 invoked by uid 48); 14 Sep 2013 15:47:08 -0000 From: "iains at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/48097] new Throw_2 failures in libjava under Xcode 4.0 Date: Sat, 14 Sep 2013 15:47:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 4.6.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: iains at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2013-09/txt/msg01065.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48097 Iain Sandoe changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2013-09-14 Ever confirmed|0 |1 --- Comment #10 from Iain Sandoe --- (In reply to Jack Howarth from comment #8) > The response to Comments 5 through 7 from the darwin linker developer is... > ------------------------------------------------------------------------- > Unfortunately, the _sigtramp function in our libSystem.dylib does not have > the 'S' letter in its augmentation string. I wrote a bug for that. With > that fixed, I'll need to verify our unwinder the properly uses that 'S' flag > to change the boundary conditions when search for the applicable FDE. > ------------------------------------------------------------------------- > So it appears that if this gets fixed, it will likely only be for darwin11. what's the expectation/status here? I see that these test-cases still fail on x86_64-darwin12, with the latest XCode tools.