public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andreas Tobler <andreast@fgznet.ch>
To: Andrew Haley <aph@redhat.com>
Cc: Jack Howarth <howarth@bromo.med.uc.edu>, java@gcc.gnu.org
Subject: Re: gcj segfaults on i686/x86_64-apple-darwin*
Date: Thu, 12 Nov 2009 23:18:00 -0000	[thread overview]
Message-ID: <4AFC9799.6060106@fgznet.ch> (raw)
In-Reply-To: <4AFBDE0E.5030103@redhat.com>

Andrew Haley wrote:
> 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.

That is what I told you, Andrew, on #irc.

>> 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.

Gcj not, but what is with ecj1? The suggestion I posted to the PR 
affects the ecjx linking.

The patchlet I posted in the 41991 PR does allow me to compile a java 
file into a class file and execute it with gij. Also the same for java 
to binary compile. This was not the case before. I went back to Jan 31 
09 and I always got an Abort with ecj1.

Note beside, I always installed the built gcc and tested the installed 
binaries.

[deuterium:~] andreast% gcj -C hello.java
[deuterium:~] andreast% gij hello
Hello World
Hello Andreas

[deuterium:~] andreast% gcj --main=testme -O testme.java
[deuterium:~] andreast% ./a.out
Hello

[deuterium:~] andreast% gcj -v
Using built-in specs.
Reading specs from 
/Volumes/development/gcc/head/testbin-x86_64/lib/gcc/x86_64-apple-darwin9/4.5.0/../../../libgcj.spec
  rename spec startfile to startfileorig
rename spec lib to liborig
COLLECT_GCC=gcj
COLLECT_LTO_WRAPPER=/Volumes/development/gcc/head/testbin-x86_64/libexec/gcc/x86_64-apple-darwin9/4.5.0/lto-wrapper
Target: x86_64-apple-darwin9
Configured with: /Volumes/development/gcc/head/gcc/configure 
--prefix=/Volumes/development/gcc/head/testbin-x86_64 
--build=x86_64-apple-darwin9 --target=x86_64-apple-darwin9 
--disable-static --with-gmp=/usr/local/x86_64 
--with-mpfr=/usr/local/x86_64 --enable-java-awt=xlib 
--enable-languages=c,c++,java
Thread model: posix
gcc version 4.5.0 20091111 (experimental) [trunk revision 153973] (GCC)


I'll run some more tests.

Andreas


  reply	other threads:[~2009-11-12 23:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-09  0:40 Jack Howarth
2009-11-09  8:56 ` Andrew Haley
2009-11-09 14:18   ` Jack Howarth
2009-11-09 14:33     ` Andrew Haley
2009-11-09 15:31       ` Jack Howarth
2009-11-09 16:28         ` Andrew Haley
2009-11-09 18:26       ` David Daney
2009-11-12  2:39       ` Jack Howarth
2009-11-12 10:06         ` Andrew Haley
2009-11-12 23:18           ` Andreas Tobler [this message]
2009-11-13  0:39             ` Jack Howarth

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4AFC9799.6060106@fgznet.ch \
    --to=andreast@fgznet.ch \
    --cc=aph@redhat.com \
    --cc=howarth@bromo.med.uc.edu \
    --cc=java@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).