Re: GCJ/minGW produced executables and linux/wine

[Jeff Sturm <jsturm at one-point dot com>]

On Wed, 5 Mar 2003, Andrew Haley wrote:
> That's true only of targets to which gcj has not yet been ported.  A
> gcj port absolutely requires a working SEGV handler.

And a working MD_FALLBACK_FRAME_STATE_FOR.  Has anyone succeeded yet
implementing this macro for a non-Linux target?

> -fcheck-references is a half-baked workaround.

-fcheck-references isn't that terrible really.  It adds a little to code
size but has a negligible effect on runtime, since the branch outcome is
easy to predict.

It also may avoid certain pessimizations resulting from
-fnon-call-exceptions.

-fcheck-references has no effect on native code, but that's probably
fixable.  (I wonder what other VM's do?  Rely on signal handling or
explicitly test each pointer?)

> -fcheck-references is the configuration default unless we're using
> sjlj.  sjlj is deprecated in gcc and will not be supported for ever.

You are correct.  Sjlj is indeed the odd case.

>  > > Please let me know which tests still fail.
>
> Throw_2 passes?
>
> Wow, that's *really* weird.  It's supposed to detect the case when
> there is not a working SEGV handler, even with -fcheck-references.
>
> That is bad news.  I would love to know _how_ that test passes.

No idea.  On a hunch, I'm starting a build with no-gc.

Jeff