This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [Patch] java PR 12734

From: Tom Tromey <tromey at redhat dot com>
To: Ralph Loader <suckfish at ihug dot co dot nz>
Cc: java-patches at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
Date: 30 Sep 2003 16:09:01 -0600
Subject: Re: [Patch] java PR 12734
References: <1064952787.13456.239.camel@localhost.localdomain><87fzie3r7h.fsf@fleche.redhat.com><1064959929.13456.310.camel@localhost.localdomain>
Reply-to: tromey at redhat dot com

>>>>> "Ralph" == Ralph Loader <suckfish@ihug.co.nz> writes:

Ralph> Are the instructions at
Ralph> http://oss.software.ibm.com/developerworks/oss/cvs/jikes/~checkout~/jacks/jacks.html
Ralph> good enough?  If not, more info appreciated.

Check out jacks as they say.
Then make a symlink gcc/libjava/testsuite/libjava.jacks/jacks that
points at the jacks checkout.

After this, "make check" will automatically run the jacks tests, and
will filter out the expected fails.

This still isn't perfect, though.  If gcj crashes when running a jacks
test, we won't notice (if the test is one where the compiler is
expected to reject the input).

Tom

References:
- [Patch] java PR 12734
  - From: Ralph Loader
- Re: [Patch] java PR 12734
  - From: Tom Tromey
- Re: [Patch] java PR 12734
  - From: Ralph Loader

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]