From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32267 invoked by alias); 31 Oct 2012 01:31:26 -0000 Received: (qmail 32251 invoked by uid 22791); 31 Oct 2012 01:31:25 -0000 X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,TW_GC,TW_IB X-Spam-Check-By: sourceware.org Received: from ainaz.pair.com (HELO ainaz.pair.com) (209.68.2.66) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 31 Oct 2012 01:30:48 +0000 Received: from k60.suse.de (charybdis-ext.suse.de [195.135.221.2]) by ainaz.pair.com (Postfix) with ESMTPSA id 3876F3F40F; Tue, 30 Oct 2012 21:30:46 -0400 (EDT) Date: Wed, 31 Oct 2012 01:31:00 -0000 From: Gerald Pfeifer To: gcc-patches@gcc.gnu.org, java-patches@gcc.gnu.org Subject: [wwwdocs,Java] Remove java/libgcj-platforms.html Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Mailing-List: contact java-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: java-patches-owner@gcc.gnu.org X-SW-Source: 2012-q4/txt/msg00015.txt.bz2 When trying to address some issues with this page, I realized it is not linked, and hasn't for probably a decade or more. And the contents is not up-to-date either or more or less covered elsewhere. Sooo, gone it is. Gerald 2012-10-31 Gerald Pfeifer * libgcj-platforms.html: Remove. Index: libgcj-platforms.html =================================================================== RCS file: libgcj-platforms.html diff -N libgcj-platforms.html --- libgcj-platforms.html 31 Oct 2002 14:47:43 -0000 1.22 +++ /dev/null 1 Jan 1970 00:00:00 -0000 @@ -1,235 +0,0 @@ - - - -libgcj-2.95 Platform Test Strategy - - - - -

libgcj-2.95 Platform Test Strategy

- -

Platform Coverage

-

One of the critical steps in making releases is platform testing. -Since there is no prior release of libgcj to perform regressions against, -we want to compare results against a known building platform, i686-pc-linux-gnu.

- -

We would like to get the widest coverage possible, so please check the -following chart for platforms that have already been covered if you have -a choice of platforms to build upon.

- -

Please send build/test results (in the format described below) to -java@gcc.gnu.org. -
You may also address questions to -java-discuss -or to indicate that you would like to help in another way with some phase of the -libgcj-2.95 release cycle.

- -

How to run the tests

- -

First, you must have built and installed -libgcj using the -libgcj-2_95-branch branch of the source.

-

This can be done by including the '-rlibgcj-2_95-branch' -flag on the 'cvs co' command line or downloading the -snapshot -and then following the - -build instructions on the libgcj page. -(For those developers downloading via snapshots, please note that -the snapshoting process has been temporarily changed to use the -libgcj-2_95-branch rather than the main trunk. -Please be aware of this if you are looking for patches that get applied -to the main source tree but not to the branch).

- -

Next, go to the libjava/testsuite directory of your build -tree and run 'make check' after doing the following:

-
    -
  • In order to more fully exercise libgcj, it is highly recommended to - include the - Mauve testsuite - in the test run. -
    The Mauve tests are available for - download - via both anonymous cvs and snapshots.
    • -
  • The env variable MAUVEDIR must be set to the top of the Mauve source tree.
    • -
  • The testsuites rely on the dejagnu package. You can download the - current dejagnu snapshot - from gcc. Please note that some earlier versions of dejagnu are missing a - patch that's in recent snapshots. Please make sure you have tried - running the testsuites with the current snapshot of dejagnu before reporting - any testsuite platform problems. There is a short entry in the - gcc FAQ - if you would like more information about this issue.
    • -
- -

Testing notes

-
    -
  • By default, tests that first compile to bytecode use an installed - javac program. Set the environment variable JAVAC - to 'gcj -C' to use the installed gcj for this purpose.
    • -
  • It is highly recommended that you not override the default libgcj - configuration option for building with dynamic libraries. This is to avoid - having to explicitly specify some libgcj object modules on the link line - to get certain java/net Mauve tests to execute.
    • -
  • An gcc patch affecting gcj was made on 24-June-99. - Developers using cvs to access the gcc source should update an rebuild - to get that fix. The next - gcc snapshot - with this patch will not be available until 30-June-99. At that point - developers without cvs access should download that patch. In the - meantime, the problem can be avoided in test runs with the following - RUNTESTFLAGS options: - 
    -   make RUNTESTFLAGS='GCJ_UNDER_TEST="gcj -L/x2/java/build/i686-pc-linux-gnu/libjava"' \
-   JAVAC='gcj -C -I/x2/java/build/i686-pc-linux-gnu/libjava/libgcj.zip' \
-   GCJ_UNDER_TEST='gcj -L/x2/java/install/lib' check
-
    - i.e. GCJ_UNDER_TEST needs a -L pointing to the libjava build directory and - JAVAC needs a -I pointing to the zip file.
    • -
- -

Current Platform Testing Status

-

This is the current results for the platforms reported to us. Please use -this format when reporting your results. -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-Platform - -Configuration - -Build Status - -Test Results -
-i686-pc-linux-gnu - ---enable-threads=posix - -OK - -# of expected passes 1876 -
-# of unexpected failures 32 -
-# of expected failures 6 -
-alphapca56-unknown-linux-gnu - ---enable-threads=posix -
--enable-fast-character -
--enable-java-gc=boehm -		 -OK - -# of expected passes 187 -
-# of unexpected failures 19 -
-# of expected failures 18 -
-sparc-sun-solaris2.6 - - -OK - -# of expected passes 60 -
-# of unexpected failures 68 -
-# of expected failures 96 -
-sparc-sun-solaris2.7 - ---enable-java-gc=no - -OK - -# of expected passes 196 -
-# of unexpected failures 22 -
-# of expected failures 8 -
- -

A list of deviations from the -posted baseline list of test results -should follow any entry you submit. -A context diff is fine if it is clear what tests are failing; -we'd rather not have to deal with a complete output listing unless -it is necessary to comprehend the deviations.

-

Note that if you are not using POSIX threads, some tests will not complete -successfully, so differences should be expected.

- -

Please send build/test results to -java@gcc.gnu.org -in this format.

- -

Submitting Patches

-

libgcj-2.95 should be considered frozen except for low-risk -porting changes that increase coverage to new target platforms -(i.e. those changes that would not affect other platforms). -High priority changes will be determined and considered on a case -by case basis. All other changes will only go into the main trunk -and not the libgcj-2_95-branch.

- -

The mailing list, -java-patches@gcc.gnu.org -has been created for patch submissions. -We plan to use this list just as gcc uses the gcc-patches list: all -patches will be sent to the list. -If you have a patch you want considered, please send it there along -with an explanation and a ChangeLog entry.

- -

Developers with checkin-after-approval access should also send patches -to this list, and then check them in after approval is given. -Developers with direct checkin access should also send patches to this -list; this can happen concurrently with the checkin.

- -

Some discussion will probably take place on this list (just as with -gcc-patches). The -web page has subscription info, -as well as a - -link to the archives.

- -

The -java-patches -mailing list is for patches to the libgcj code -(libjava, boehm-gc, zlib, etc) code only. -In particular, compiler patches still have to go through gcc, so -please don't send them to java-patches.

- - -