Re: gcj segfaults on i686/x86_64-apple-darwin*
Andrew Haley <[email protected]>
| Newsgroups | gmane.comp.gcc.java.devel |
|---|---|
| Message-ID | <[email protected]> |
Jack Howarth wrote: > On Mon, Nov 09, 2009 at 02:33:11PM +0000, Andrew Haley wrote: >> Jack Howarth wrote: >> >>> Shouldn't the libjava testsuite contain some rudimentary tests using gcj >>> to make sure it is functional? >> Sure. >> >>> The recent testsuite results don't suggest >>> major problems with java on intel darwin... >>> >>> http://gcc.gnu.org/ml/gcc-testresults/2009-11/msg00666.html >>> http://gcc.gnu.org/ml/gcc-testresults/2009-10/msg01308.html >> This means that, whatever the cause of the bug, it wasn't present >> when these tests were run. >> >> You can easily verify that yourself by running 'make check-target-libjava'. > Actually the nature of the testsuite will mask this failure on intel darwin. > The gcj compiler doesn't segfault when presented with a *.class file to compile > into an executable. Only when presented a *.java file will the gcj compiler abort. In that case, gcj isn't aborting. gcj only ever compiles .class -> .o, where .java -> .class compilation is performed by ecj1. > I suspect if the libjava harness was fixed to compile the java files if a ecj1 was > built that all of the libjava.lang tests would suddenly fail on darwin. Andreas Tobler Seems to think it's to do with stack execution, but I can't understand how that can be: gcj doesn't generate executable code on the stack. Andrew.