--- Comment #9 from hjl dot tools at gmail dot com 2009-08-24 15:48 ---
Fixed:
http://gcc.gnu.org/ml/gcc-testresults/2009-08/msg02467.html
--
hjl dot tools at gmail dot com changed:
What|Removed |Added
--- Comment #8 from aph at gcc dot gnu dot org 2009-08-03 17:55 ---
Subject: Bug 40867
Author: aph
Date: Mon Aug 3 17:55:11 2009
New Revision: 150376
URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=150376
Log:
2009-07-31 Andrew Haley a...@redhat.com
PR java/40867
--- Comment #7 from rguenther at suse dot de 2009-07-31 09:19 ---
Subject: Re: [4.5 Regression] FAIL: StackTrace2 output
- source compiled test
On Thu, 30 Jul 2009, aph at gcc dot gnu dot org wrote:
--- Comment #6 from aph at gcc dot gnu dot org 2009-07-30 17:24 ---
This
--- Comment #3 from aph at gcc dot gnu dot org 2009-07-30 07:37 ---
This regression in debuginfo seems to have been downgraded to P4, with no
explanation or discussion of which I'm aware.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40867
--- Comment #4 from joseph at codesourcery dot com 2009-07-30 11:24 ---
Subject: Re: [4.5 Regression] FAIL: StackTrace2 output
- source compiled test
On Thu, 30 Jul 2009, aph at gcc dot gnu dot org wrote:
This regression in debuginfo seems to have been downgraded to P4, with no
--- Comment #5 from aph at gcc dot gnu dot org 2009-07-30 11:36 ---
Hmm, this seems to me as a rather perverse interpretation of the rule that
Java issues are not release-critical: this bug may be manifested in Java
programs, but there is no evidence of which I'm aware that this
--- Comment #6 from aph at gcc dot gnu dot org 2009-07-30 17:24 ---
This seems to be happening very early, because the very first tree dump shows:
StackTrace2$Inner.doCrash(java.lang.Object) (struct StackTrace2$Inner * this,
struct java.lang.Object * o)
[StackTrace2.java : 0:0] {
--
jsm28 at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P4
Target Milestone|--- |4.5.0
--- Comment #2 from aph at gcc dot gnu dot org 2009-07-28 08:02 ---
This is actually a regression in debuginfo: the line number info is being
corrupted, somewhere after the front end. I don't know if this was caused by
the gimplify unit-at-a-time patch.
--
aph at gcc dot gnu dot
