From: "Andrew John Hughes" <gnu_andrew@member.fsf.org>
To: mauve-patches@sources.redhat.com
Subject: [builder] FYI: Add JikesRVM to JAPI runs
Date: Fri, 01 Feb 2008 01:04:00 -0000 [thread overview]
Message-ID: <20080201010405.GA19226@localhost.localdomain> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 450 bytes --]
This compares Classpath with JikesRVM's runtime files
as part of the JAPI run. The JikesRVM file is currently
added manually until we have this running on builder.
ChangeLog:
2008-02-01 Andrew John Hughes <gnu_andrew@member.fsf.org>
* RunJapi: Add JikesRVM comparison.
--
Andrew :-)
Escape the Java Trap with GNU Classpath!
http://www.gnu.org/philosophy/java-trap.html
public class gcj extends Freedom implements Java { ... }
[-- Attachment #1.2: japi-02.diff --]
[-- Type: text/x-diff, Size: 950 bytes --]
Index: scripts/RunJapi
===================================================================
RCS file: /cvs/mauve/builder/scripts/RunJapi,v
retrieving revision 1.3
diff -u -3 -p -u -r1.3 RunJapi
--- scripts/RunJapi 30 Jan 2008 20:28:59 -0000 1.3
+++ scripts/RunJapi 1 Feb 2008 01:00:19 -0000
@@ -79,6 +79,10 @@ $JAPITOOLS/bin/japicompat -v -h -o openj
openjdk-b12.japi.gz libgcj.japi.gz
$JAPITOOLS/bin/japicompat -v -h -o libgcj-openjdk.html \
libgcj.japi.gz openjdk-b12.japi.gz
+$JAPITOOLS/bin/japicompat -v -h -o jikesrvm-classpath.html \
+ jikesrvm.japi.gz classpath.japi.gz
+$JAPITOOLS/bin/japicompat -v -h -o classpath-jikesrvm.html \
+ classpath.japi.gz jikesrvm.japi.gz
# Now publish the result
cp jdk14-classpath.html $WEB/
@@ -93,3 +97,5 @@ cp openjdk-libgcj.html $WEB/
cp libgcj-openjdk.html $WEB/
cp $ONExONE $WEB/
cp $CSS $WEB/
+cp jikesrvm-classpath.html $WEB/
+cp classpath-jikesrvm.html $WEB/
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2008-02-01 1:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20080201010405.GA19226@localhost.localdomain \
--to=gnu_andrew@member.fsf.org \
--cc=mauve-patches@sources.redhat.com \
/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).