What's up with jc1 segfaulting on mingw target? [PR 5876]

[Adam Megacz <gcj at lists dot megacz dot com>]

Guys, this is getting worse.

As of yesterday, gcj segfaults even with Jeff's patch (even after
Jan's fixes from this morning). See my last post for the specific
failure.

I hate to sound whiney like this, but is anybody ever going to look
into why gcj segfaults when compiling code for a mingw target? I
simply don't have the time or skill to get involved in front-end
work. If nobody else is interested in fixing it, please let me know
before I waste any more time on porting libgcj.

  - a


Jeff Sturm <jsturm@one-point.com> writes:
> On 5 Mar 2002, Adam Megacz wrote:
> > Basically, I'd love to see mingw-gcj in 3.1, but it's sorta stupid for
> > me to stress over it if the front end is going to remain broken.

> I'm of the opinion this should be a high-priority PR.  It's a regression
> over 3.0, after all.

> If nothing else, what do others think about backing out the offending
> patch on 3.1 only?


-- 
"If I put copyrighted material into the 'chewy nougat center', I can
 claim the crunchy chocolate coating is an 'Access Control
 Mechanism'."                                     --lynx_user_abroad

Why Windows NT/2k/XP is unreliable: www.zappadoodle.com