This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
[XHTML 1.0] java subdir
- From: Andrea 'Fyre Wyzard' Bocci <fwyzard at inwind dot it>
- To: gcc-patches at gcc dot gnu dot org,java-patches at gcc dot gnu dot org
- Cc: Tom Tromey <tromey at redhat dot com>,Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>
- Date: Sat, 23 Mar 2002 23:34:23 +0100
- Subject: [XHTML 1.0] java subdir
HI !
I've almost finished converting the java subdir for XHTML 1.0 compliance.
This patch addresses all the files in wwwdocs/htdocs/java , except faq.html
(already corrected) and faq-portugese.html (still working on that).
There are also some correction to the GCJ side bar - I'm sending those with
a separte patch vs. style.mhtml.
With those changes, all these pages validated with the W3C validator as
XHTML 1.0 Transitional.
The patched pages are available at
<http://studenti.fisica.unifi.it/~fwyzard/gcc/>.
The XHTML compliantness status is available at
<http://studenti.fisica.unifi.it/~fwyzard/validgcc.html>.
The portugese FAQ is a bit outdated. I can make it XHTML compliant, and
also point out the discrepancies (portugese is not far from italian, if you
know what it should mean).
Is anybody going to update that ? In any case, I'll make it compliant, and
post a patch.
Some documents in the java/papers subdirectory are SGML generated. Instead
of correcting them, is possible to re-generate them in XHTML ?
fwyzard
Index: java/build-snapshot.html
===================================================================
RCS file: /cvsroot/gcc/wwwdocs/htdocs/java/build-snapshot.html,v
retrieving revision 1.14
diff -u -3 -p -r1.14 build-snapshot.html
--- java/build-snapshot.html 14 Sep 2001 20:57:38 -0000 1.14
+++ java/build-snapshot.html 23 Mar 2002 22:05:12 -0000
@@ -17,7 +17,7 @@
<tr bgcolor="#cccccc">
<td>
<pre>
-General gcj download information can be found <A HREF="download.html">here</A>.
+General gcj download information can be found <a href="download.html">here</a>.
1a. <a href="../snapshots.html">Get a GCC snapshot.</a>
@@ -64,7 +64,7 @@ you get Libgc from an other cvs or snaps
Have a look at the toplevel configure.in (gcc/configure.in) and
make sure that the variable `noconfigdirs' isn't assigned to
something (like target-libjava or ${libgcj}.)
-<br>
+<br />
Also, check for platform-specific assignments of `noconfigdirs' with
${libgcj}; if ${libgcj} is listed for your platform, remove it before
configuring.
@@ -97,7 +97,7 @@ installing gcc and/or configuration opti
If you have a broken gas/bin-utils (such as Debian potato) then you
want to edit the auto-host.h file and remove the definition of
HAVE_GAS_HIDDEN after configuring, but before typeing make. See
-<a href=faq.html#5_7>the FAQ</a> for more information.
+<a href="faq.html#5_7">the FAQ</a> for more information.
</pre>
</td>
</tr>
Index: java/compile.html
===================================================================
RCS file: /cvsroot/gcc/wwwdocs/htdocs/java/compile.html,v
retrieving revision 1.4
diff -u -3 -p -r1.4 compile.html
--- java/compile.html 3 Feb 2002 02:25:16 -0000 1.4
+++ java/compile.html 23 Mar 2002 22:05:12 -0000
@@ -6,7 +6,7 @@
<body>
-<h2 align=center>Compiling with GCJ</h2>
+<h2 align="center">Compiling with GCJ</h2>
<h2>Introduction</h2>
@@ -15,7 +15,7 @@
input and compile architecture-specific object files. Second, by
using the -C option, GCJ can take .java files as input, and
generate .class files. Third, GCJ can take .class files as input
- to create architecture-specific object files.
+ to create architecture-specific object files.</p>
<p>GCJ offers two run-time support libraries, libgcj and libgcjgc.
libgcj is a clean-room implementation of the core Java
@@ -25,17 +25,17 @@
Java objects precisely and has changes to work with the
cooperative threads-package. It uses a basic mark-sweep
algorithm to perform the actual collections, stopping all
- threads as it works.
+ threads as it works.</p>
<h2>Compiling Java Programs</h2>
<p>If you are working with Java, we recommend you use the gcj program
-instead of using GCC directly.
+instead of using GCC directly.</p>
<h3>Java-specific file extensions</h3>
<p>GCJ (GNU Compiler for Java) deals with the following Java-specific
-file extensions, and you can specify any of these as an input file:
+file extensions, and you can specify any of these as an input file:</p>
<dl>
<dt>.java</dt>
@@ -70,7 +70,7 @@ included.) GCJ treats it the same as a
<h3>GCJ command-line options</h3>
<p>In addition to the normal GCC options, GCJ recognizes the following
-options:
+options:</p>
<dl>
<dt>-C</dt>
@@ -150,7 +150,7 @@ directories or file names.</dd>
</dl>
-<p>Here are some other points worth noting:
+<p>Here are some other points worth noting:</p>
<ul>
<li> If there is no -g or -O option (and no options starting with those
@@ -159,10 +159,10 @@ directories or file names.</dd>
information to be generated, but not the other information necessary
for source-level debugging. The reason for this change is partly for
compatibility with Sun's tools, and partly because it is helpful
- when printing an exceptions stack trace.
+ when printing an exceptions stack trace.</li>
<li> When an application is linked, gcj will also link in the standard
- Java run-time libraries (libgcj, and possibly others).
+ Java run-time libraries (libgcj, and possibly others).</li>
</ul>
</body>
Index: java/contrib.html
===================================================================
RCS file: /cvsroot/gcc/wwwdocs/htdocs/java/contrib.html,v
retrieving revision 1.27
diff -u -3 -p -r1.27 contrib.html
--- java/contrib.html 9 Oct 2001 17:23:52 -0000 1.27
+++ java/contrib.html 23 Mar 2002 22:05:12 -0000
@@ -6,9 +6,9 @@
<body>
-<GCJNAV>
+<gcjnav>
-<br><br>
+<br /><br />
<h1>Contributing to the GCJ Project</h1>
<table border="0" cellpadding="4" width="95%">
@@ -18,12 +18,10 @@
</th>
</tr>
</table>
-<br>
+<br />
<p>We've started maintaining a list of <a href="projects.html">useful
-projects</a>.
-
-<p>
+projects</a>.</p>
<table border="0" cellpadding="4" width="95%">
<tr bgcolor="#b0d0ff">
@@ -32,33 +30,31 @@ projects</a>.
</th>
</tr>
</table>
-<br>
+<br />
<p>All contributions must conform to the <a
href="http://www.gnu.ai.mit.edu/prep/standards_toc.html";>GNU Coding
Standards</a>. Submissions which do not conform to the standards will
- be returned with a request to reformat the changes.
+ be returned with a request to reformat the changes.</p>
<p>Note that the GNU Coding Standards do not actually cover Java
programming style. libgcj largely uses the obvious extrapolation
- from the GNU C style, but there are some differences.
+ from the GNU C style, but there are some differences.</p>
- <p>The changes are something like this:
+ <p>The changes are something like this:</p>
<ul>
- <li> Open braces go on a new line (like GNU C style)
+ <li> Open braces go on a new line (like GNU C style) </li>
- <li> Two space indent for methods and inner classes
+ <li> Two space indent for methods and inner classes </li>
<li> <tt>if</tt>, <tt>try</tt>, <tt>for</tt>, and
<tt>synchronized</tt> blocks are indented four spaces (the braces are
- indented two spaces, then the code an additional two spaces)
+ indented two spaces, then the code an additional two spaces) </li>
<li> The open brace for a method body is indented only as far as the
- method header
+ method header </li>
</ul>
- <p>
-
<table border="0" cellpadding="4" width="95%">
<tr bgcolor="#b0d0ff">
<th align="left">
@@ -66,7 +62,7 @@ projects</a>.
</th>
</tr>
</table>
-<br>
+<br />
<p>Before we can accept code contributions from you, we need a
copyright assignment form filled out. See <a
@@ -82,35 +78,33 @@ projects</a>.
</th>
</tr>
</table>
-<br>
+<br />
<p>Every patch must have several pieces of information before we can
- properly evaluate it.
+ properly evaluate it.</p>
<ul>
<li> A description of the bug and how your patch fixes this bug. For
- new features a description of the feature and your implementation.
+ new features a description of the feature and your implementation.</li>
<li> A ChangeLog entry as plaintext; see the various ChangeLog files
- for format and content.<br>
+ for format and content.<br />
Note that, unlike some other projects, we do require ChangeLogs
- also for documentation (i.e., .texi files).
+ also for documentation (i.e., .texi files).</li>
<li> The patch itself. If you are accessing the
CVS repository at Red Hat, use "cvs update; cvs diff -c3p";
else, use "diff -c3p OLD NEW" or "diff -up OLD NEW".
If your version of diff does not support these options, then get the
- latest version of GNU diff.
+ latest version of GNU diff.</li>
</ul>
<p>Send <tt>libgcj</tt>patches to <a
href="mailto:java-patches@gcc.gnu.org";>the patch mailing
- list</a>. This list is <a href="http://gcc.gnu.org/ml/java-patches/";>archived</a>.
+ list</a>. This list is <a href="http://gcc.gnu.org/ml/java-patches/";>archived</a>.</p>
<p>Patches to the gcj front end -- the <tt>gcc/java</tt> directory --
should be sent to <a href="mailto:gcc-patches@gcc.gnu.org";>the gcc
patch mailing list</a>. See <a
href="../contribute.html">the GCC contribution
- instructions</a> for more information.
-
- <p>
+ instructions</a> for more information.</p>
<table border="0" cellpadding="4" width="95%">
<tr bgcolor="#b0d0ff">
@@ -119,64 +113,63 @@ projects</a>.
</th>
</tr>
</table>
-<br>
+<br />
<p>If you have direct checkin access for libgcj (meaning write
permission to the gcc repository as well as permission to commit
your patch to libgcj), please make sure that your checkins follow
- the standard checkin rules.
+ the standard checkin rules.</p>
<p>First, always make ChangeLog entries. This is not negotiable;
a checkin without a ChangeLog entry will be reverted. If the
- checkin fixes a bug in Gnats, note this in the entry.
+ checkin fixes a bug in Gnats, note this in the entry.</p>
<p>The commit message given to cvs should be the ChangeLog entry.
If you wrote the entry (your name is at the top), then don't
include the header. If someone else wrote the entry, do include
the header. It is customary to make the <tt>cvs commit</tt> log
- message the same as the ChangeLog entry.
+ message the same as the ChangeLog entry.</p>
<p>If your change fixes a PR, put the text (e.g.)
``<tt>Fixes PR java/58</tt>'' into the ChangeLog entry and into the
cvs commit message. This will cause an automatic message to be
- sent to Gnats to record the commit in the PR.
+ sent to Gnats to record the commit in the PR.</p>
<p>After checking in a fix which fixes a PR, put the PR into
``feedback'' mode. This will send email to the bug's
originator. In the change message ask them to try the fix and
- report back.
+ report back.</p>
<p>Once the originator reports back, or after some suitable amount
of time (less time if you are absolutely sure, beyond any shadow
- of a doubt, that the bug has been fixed) close the PR.
+ of a doubt, that the bug has been fixed) close the PR.</p>
- <p>
-<br>
+<br />
<table border="0" cellpadding="4" width="95%">
<tr bgcolor="#b0d0ff">
<th align="left">
- <a name=Testing>Testing</a>
+ <a name="Testing">Testing</a>
</th>
</tr>
</table>
-<br>
+<br />
- We're accepting test case patches.<br>
+ We're accepting test case patches.<br />
<ul>
<li>Put the <tt>.java</tt> file in
<tt>libjava/testsuite/libjava.compile</tt>
(if it is an expected compiler failure or other compile-time test --
- run-time tests usually go in <tt>libjava.lang</tt>)
+ run-time tests usually go in <tt>libjava.lang</tt>)</li>
<li>If the file is "<tt>foo.java</tt>" make a "<tt>foo.xfail</tt>" file.
For an expected failure the only thing in there should be
- "<tt>shouldfail</tt>"
+ "<tt>shouldfail</tt>"</li>
<li>If the test case matches a Java PR, it is customary to name it after
- the PR number.
+ the PR number.</li>
- <li>Send the patch to java-patches and then commit of you're allowed to.
+ <li>Send the patch to java-patches and then commit of you're allowed to.</li>
</ul>
<p>
@@ -184,8 +177,9 @@ projects</a>.
There is also some documentation on <a href="test.html">how to run
test cases</a>. This covers both our built-in tests and extra test
suites we use.
+</p>
-</GCJNAV>
+</gcjnav>
</body>
</html>
Index: java/docs.html
===================================================================
RCS file: /cvsroot/gcc/wwwdocs/htdocs/java/docs.html,v
retrieving revision 1.20
diff -u -3 -p -r1.20 docs.html
--- java/docs.html 29 Dec 2001 19:13:58 -0000 1.20
+++ java/docs.html 23 Mar 2002 22:05:12 -0000
@@ -6,9 +6,9 @@
<body>
-<GCJNAV>
+<gcjnav>
-<br><br>
+<br /><br />
<h1>GCJ Documentation</h1>
<table border="0" cellpadding="4" width="95%">
@@ -18,20 +18,20 @@
</th>
</tr>
</table>
-<br>
+<br />
<ul>
- <li>General <a href="gcj2.html">gcj</a> information.
- <li>General <a href="libgcj2.html">runtime</a> information.
- <li>How to <a href="compile.html">compile</a> a Java program.
- <li>How to <a href="gdb.html">debug</a> a Java program using GDB.
- <li><a href="faq.html">Frequently Asked Questions</a>
- <li>How to <a href="contrib.html">contribute</a>
- <li><a href="papers/cni/t1.html">CNI Documentation</a>
+ <li>General <a href="gcj2.html">gcj</a> information.</li>
+ <li>General <a href="libgcj2.html">runtime</a> information.</li>
+ <li>How to <a href="compile.html">compile</a> a Java program.</li>
+ <li>How to <a href="gdb.html">debug</a> a Java program using GDB.</li>
+ <li><a href="faq.html">Frequently Asked Questions</a>.</li>
+ <li>How to <a href="contrib.html">contribute</a>.</li>
+ <li><a href="papers/cni/t1.html">CNI Documentation</a>.</li>
</ul>
-<br>
+<br />
<table border="0" cellpadding="4" width="95%">
<tr bgcolor="#b0d0ff">
<th align="left">
@@ -39,18 +39,18 @@ Porting the GCJ runtime.
</th>
</tr>
</table>
-<br>
+<br />
We've written three documents on how to port various components of
GCJ runtime, libgcj, to different target systems.
<ul>
-<li>How to <a href="port-threads.html">port</a> the thread layer.
-<li>How to <a href="port-files.html">port</a> the file handling layer.
-<li>How to <a href="port-signals.html">port</a> the signal handling layer.
+<li>How to <a href="port-threads.html">port</a> the thread layer.</li>
+<li>How to <a href="port-files.html">port</a> the file handling layer.</li>
+<li>How to <a href="port-signals.html">port</a> the signal handling layer.</li>
</ul>
-<br>
+<br />
<table border="0" cellpadding="4" width="95%">
<tr bgcolor="#b0d0ff">
<th align="left">
@@ -58,38 +58,38 @@ Papers describing our work
</th>
</tr>
</table>
-<br>
+<br />
<p>The engineers on this project have written a number of papers for
-conferences and magazines.
+conferences and magazines.</p>
<ul>
<li><a name="CNI">
- <b>February 1999</b>: "<cite>The Cygnus Native Interface for C++/Java Integration</cite>".
- <br>[<a href="papers/cni/t1.html">HTML</a>]
- [<a href="papers/cni.sgml">SGML/Docbook source</a>]
- <br>This is a programmer's manual which explains how to use
+ <b>February 1999</b>: "<cite>The Cygnus Native Interface for C++/Java Integration</cite>".</a>
+ <br />[<a href="papers/cni/t1.html">HTML</a>]
+ [<a href="papers/cni.sgml">SGML/Docbook source</a>]
+ <br />This is a programmer's manual which explains how to use
a Java-aware C++ compiler (G++) to write native methods for Gcj.
- <br>The CNI design and ideas were proposed in
+ <br />The CNI design and ideas were proposed in
"<cite>Writing native Java methods in natural C++</cite>"
- (November 1997).</a>
- <p>
+ (November 1997).
+ </li>
<li><b>August 1998</b>: "<cite>No Silver Bullet - Garbage Collection for
Java in Embedded Systems</cite>".
- <br>[<a href="papers/nosb.html">HTML</a>]
- [<a href="papers/nosb.ps.gz">PS for presentation slides</a>]
- <br>Author: Alex Petit-Bianco.
- <p>
+ <br />[<a href="papers/nosb.html">HTML</a>]
+ [<a href="papers/nosb.ps.gz">PS for presentation slides</a>]
+ <br />Author: Alex Petit-Bianco.
+ </li>
<li><b>November 1997</b>: "<cite>Writing native Java methods in natural C++</cite>"
discusses interaction between Java and C++. This is an early design
document; see "<cite>The Cygnus Native Interface for C++/Java
Integration</cite>" (February 1998) for the programmer's manual.
- <br>[<a href="papers/native++.html">HTML</a>]
- [<a href="papers/native++.sgml">SGML/Docbook source</a>]
- <br>Author: <a href="http://www.bothner.com/";>Per Bothner</a>.
- <p>
+ <br />[<a href="papers/native++.html">HTML</a>]
+ [<a href="papers/native++.sgml">SGML/Docbook source</a>]
+ <br />Author: <a href="http://www.bothner.com/";>Per Bothner</a>.
+ </li>
<li><b>October 1997</b>: "<cite>Compiling Java for Embedded
Systems</cite>" was presented by Per Bothner at the Embedded
@@ -97,31 +97,31 @@ conferences and magazines.
overview of our strategy and plans at the time. This is fairly
out of date now.
- <br>[<a href="papers/compjava.pdf">PDF</a>]
- [<a href="papers/compjava.ps.gz">gzip'd Postscript</a>]
- [<a href="papers/esc97.sgml">SGML/Docbook source</a>]
- [<a href="papers/esc97w-slides.ps.gz">PS
- for presentation slides</a>].
+ <br />[<a href="papers/compjava.pdf">PDF</a>]
+ [<a href="papers/compjava.ps.gz">gzip'd Postscript</a>]
+ [<a href="papers/esc97.sgml">SGML/Docbook source</a>]
+ [<a href="papers/esc97w-slides.ps.gz">PS
+ for presentation slides</a>].
- <br>Author: <a href="http://www.bothner.com/";>Per Bothner</a>.
- <p>
+ <br />Author: <a href="http://www.bothner.com/";>Per Bothner</a>.
+ </li>
<li><b>February 1997</b>: "<cite>A Gcc-based Java Implementation</cite>" is an older paper
presented by Per Bothner
at IEEE Compcon.
- <br>[<a href="papers/gcc-java.html">extended
- abstract (HTML)</a>]
- [<a href="papers/gcc-java.ps.gz">complete
- paper (Postscript)</a>]
- [(<a href="papers/compcon97.ps.gz">slides
- for presentation</a>)]
+ <br />[<a href="papers/gcc-java.html">extended
+ abstract (HTML)</a>]
+ [<a href="papers/gcc-java.ps.gz">complete
+ paper (Postscript)</a>]
+ [(<a href="papers/compcon97.ps.gz">slides
+ for presentation</a>)]
- <br>Author: <a href="http://www.bothner.com/";>Per Bothner</a>.
- <p>
+ <br />Author: <a href="http://www.bothner.com/";>Per Bothner</a>.
+ </li>
</ul>
-</GCJNAV>
+</gcjnav>
</body>
</html>
Index: java/done.html
===================================================================
RCS file: /cvsroot/gcc/wwwdocs/htdocs/java/done.html,v
retrieving revision 1.26
diff -u -3 -p -r1.26 done.html
--- java/done.html 21 Mar 2002 04:28:40 -0000 1.26
+++ java/done.html 23 Mar 2002 22:05:13 -0000
@@ -6,29 +6,29 @@
<body>
-<GCJNAV>
+<gcjnav>
- <br>
- <br>
+ <br />
+ <br />
<h1>Done with GCJ</h1>
This page provides descriptions and links on projects
that are using the GCJ runtime and compiler. If you would like
your project to be listed here or know about a particular
- project, please write to the <A
- HREF="mailto:java@gcc.gnu.org";>list</A>.
+ project, please write to the <a
+ href="mailto:java@gcc.gnu.org";>list</a>.
<p>
Entries are now listed in chronological order.
+ </p>
- <p>
<table border="0" cellpadding="1" cellspacing="2"
- fgcolor="#ff0000" rules="all" width="98%">
- <tr bgcolor="#d0d0d0" valign=top>
+ rules="all" width="98%">
+ <tr bgcolor="#d0d0d0" valign="top">
<td>Project</td><td>Description</td><td>Contact</td>
</tr>
<!-- XWT -->
- <tr valign=top>
- <td><B>XWT</B></td>
+ <tr valign="top">
+ <td><b>XWT</b></td>
<td>XWT is the XML Windowing Toolkit. It lets you write remote
applications -- applications that run on a server, yet can
@@ -38,16 +38,16 @@
an ActiveX control.
</td>
- <td>The <A HREF="http://www.xwt.org";>XWT</A> home page.
- <A HREF="http://gcc.gnu.org/ml/java/2002-01/msg00101.html";>
- Entry</A> submitted by <A HREF="mailto:gcj@lists.megacz.com";>
- Adam Megacz</A>.
+ <td>The <a href="http://www.xwt.org";>XWT</a> home page.
+ <a href="http://gcc.gnu.org/ml/java/2002-01/msg00101.html";>
+ Entry</a> submitted by <a href="mailto:gcj@lists.megacz.com";>
+ Adam Megacz</a>.
</td>
</tr>
<!-- End XWT -->
<!-- Autonomous Haulage -->
- <tr valign=top>
- <td><B>Autonomous Haulage</B></td>
+ <tr valign="top">
+ <td><b>Autonomous Haulage</b></td>
<td>Modular Mining System is using gcj on an embedded
StrongARM processor to control autonomous trucks in mining haulage
@@ -55,17 +55,17 @@
in-house runtime that they wrote.
</td>
- <td>The <A HREF="http://www.mmsi.com/modular/trucks/index.html";>
- Autonomous Truck Page</A>.
- <A HREF="http://gcc.gnu.org/ml/java/2000-06/msg00086.html";>
- Entry</A> submitted by <A HREF="mailto:olson@mmsi.com";>Jon
- Olson</A>.
+ <td>The <a href="http://www.mmsi.com/modular/trucks/index.html";>
+ Autonomous Truck Page</a>.
+ <a href="http://gcc.gnu.org/ml/java/2000-06/msg00086.html";>
+ Entry</a> submitted by <a href="mailto:olson@mmsi.com";>Jon
+ Olson</a>.
</td>
</tr>
<!-- End Autonomous Haulage -->
<!-- jUSB/jPhoto -->
- <tr valign=top>
- <td><B>jUSB/jPhoto</B></td>
+ <tr valign="top">
+ <td><b>jUSB/jPhoto</b></td>
<td>jUSB is an open source Java API for USB, with an
implementation that runs on recent GNU/Linux OS
@@ -73,26 +73,26 @@
jPhoto provides basic command line and library support for
the digital camera protocol on top of jUSB. The protocol is the
- new USB standard for talking to such devices called <A
- HREF="http://www.pima.net/standards/it10/PIMA15740/";>PTP</A>.
+ new USB standard for talking to such devices called <a
+ href="http://www.pima.net/standards/it10/PIMA15740/";>PTP</a>.
</td>
- <td>The <A HREF="http://jusb.sourceforge.net";>jUSB</A>
- page. The <A HREF="http://jphoto.sourceforge.net";>JPhoto</A>
- page. <A HREF="http://gcc.gnu.org/ml/java/2000-11/msg00112.html";>Entry</A>
- submitted by <A HREF="mailto:david-b@pacbell.net";>David
- Brownell</A>.
+ <td>The <a href="http://jusb.sourceforge.net";>jUSB</a>
+ page. The <a href="http://jphoto.sourceforge.net";>JPhoto</a>
+ page. <a href="http://gcc.gnu.org/ml/java/2000-11/msg00112.html";>Entry</a>
+ submitted by <a href="mailto:david-b@pacbell.net";>David
+ Brownell</a>.
</td>
</tr>
<!-- End jUSB/jPhoto -->
<!-- PAL -->
- <tr valign=top>
- <td><B>PAL</B></td>
+ <tr valign="top">
+ <td><b>PAL</b></td>
<td>PAL is a Java library for use in molecular evolution and
phylogenetics. Basically, PAL includes classes and
methods for computationally intensive statistics that are
- useful for the analysis of DNA sequences.<p>
+ useful for the analysis of DNA sequences.<br />
PAL 1.0 consists of 111 classes in 12 packages with more than
20,000 lines of code, all of which compiles nicely into native
@@ -107,8 +107,8 @@
</tr>
<!-- End PAL -->
<!-- Swarm -->
- <tr valign=top>
- <td><B>Swarm</B></td>
+ <tr valign="top">
+ <td><b>Swarm</b></td>
<td>Swarm is a fine-grained distributed discrete event
simulator. Swarm is mainly used for agent-based
@@ -121,15 +121,15 @@
with gcj support. On Intel Debian 2.2, up to 30%
performance gains over Kaffe's jit3 were witnessed.
</td>
- <td><A HREF="http://www.swarm.org";>Swarm</A>.
- <A HREF="http://gcc.gnu.org/ml/java/2000-06/msg00084.html";>Entry</A>
- submitted by <A HREF="mailto:mgd@swarm.org";>Marcus G. Daniel</A>.
+ <td><a href="http://www.swarm.org";>Swarm</a>.
+ <a href="http://gcc.gnu.org/ml/java/2000-06/msg00084.html";>Entry</a>
+ submitted by <a href="mailto:mgd@swarm.org";>Marcus G. Daniel</a>.
</td>
</tr>
<!-- End Swarm -->
<!-- Tamanoir -->
- <tr valign=top>
- <td><B>Tamanoir</B></td>
+ <tr valign="top">
+ <td><b>Tamanoir</b></td>
<td>Tamanoir system is a complete framework that allows users
to easily deploy and maintain distributed active routers
on wide area networks. In the rapidly expanding field of
@@ -140,39 +140,41 @@
portability of services. It's written in Java and
standardly built using gcj.
</td>
- <td>The <A
- HREF="http://www.ens-lyon.fr/~jpgelas/TAMANOIR/";>Tamanoir</A>
- page. <A HREF="http://gcc.gnu.org/ml/java/2001-01/msg00069.html";>
- Entry</A> submitted by
+ <td>The <a
+ href="http://www.ens-lyon.fr/~jpgelas/TAMANOIR/";>Tamanoir</a>
+ page. <a href="http://gcc.gnu.org/ml/java/2001-01/msg00069.html";>
+ Entry</a> submitted by
<a href="mailto:jpgelas@lhpcm.univ-lyon1.fr";>Jean Patrick
Gelas</a>.
+ </td>
</tr>
<!-- End Tamanoir -->
<!-- Fluid Dynamics -->
- <tr valign=top>
- <td><B>Fluid Dynamics</B></td>
+ <tr valign="top">
+ <td><b>Fluid Dynamics</b></td>
<td>Alejandro Rodríguez Gallego, at ICAI University (Spain)
has spent two years developing a Java program to solve
- fluid dynamics. He says:<p>
+ fluid dynamics. He says:
- <quote>
+ <cite>
I have recently tested my program with GCJ and I have got
an incredible performance increase over HotSpot v2 (JDK 1.3 for
- linux). -50% RAM were needed and execution time reduced in -15%.<p>
-
- GCJ will be the main compiler for my program.<p>
- </quote>
+ linux). -50% RAM were needed and execution time reduced in -15%.
+ <br />
+ GCJ will be the main compiler for my program.
+ </cite>
+ </td>
+ <td>The <a
+ href="http://www.dfc.icai.upco.es/invest/adfc/adfc.html";>ADFC</a>
+ page. <a href="http://gcc.gnu.org/ml/java/2001-01/msg00228.html";>
+ Entry</a> submitted by <a href="mailto:balrog@amena.com";>
+ Alejandro Rodríguez Gallego</a>.
</td>
- <td>The <A
- HREF="http://www.dfc.icai.upco.es/invest/adfc/adfc.html";>ADFC</A>
- page. <A HREF="http://gcc.gnu.org/ml/java/2001-01/msg00228.html";>
- Entry</A> submitted by <A HREF="mailto:balrog@amena.com";>
- Alejandro Rodríguez Gallego</A>.
</tr>
<!-- End Fluid Dynamics -->
</table>
-</GCJNAV>
+</gcjnav>
</body>
</html>
Index: java/download.html
===================================================================
RCS file: /cvsroot/gcc/wwwdocs/htdocs/java/download.html,v
retrieving revision 1.31
diff -u -3 -p -r1.31 download.html
--- java/download.html 15 Dec 2001 02:31:36 -0000 1.31
+++ java/download.html 23 Mar 2002 22:05:13 -0000
@@ -6,9 +6,9 @@
<body bgcolor="white">
-<GCJNAV>
+<gcjnav>
-<br><br>
+<br /><br />
<h1>Downloading GCJ</h1>
<table border="0" cellpadding="4" width="95%">
@@ -18,15 +18,17 @@
</th>
</tr>
</table>
-<br>
+<br />
+<p>
The most current official release of GCJ and libgcj is 3.0.2, which is included
with the GCC 3.0.2 source distribution.
+</p>
<p>
Follow the links on <a href="http://gcc.gnu.org/releases.html";>http://gcc.gnu.org/releases.html</a>
to download the compiler. You will need either the full distribution,
or each of the Core Compiler, C++ and Java distributions.
-<p>
+</p>
<table border="0" cellpadding="4" width="95%">
@@ -36,11 +38,13 @@ or each of the Core Compiler, C++ and Ja
</th>
</tr>
</table>
+<br />
+
<p>
Many GNU/Linux distributions now include relatively recent, "QA'ed" versions of
GCJ which should work out-of-the-box. Look for packages like "gcc-java" and
"gcc-libgcj" to add Java language support to your existing GCC installation.
-<p>
+</p>
<table border="0" cellpadding="4" width="95%">
<tr bgcolor="#b0d0ff">
@@ -49,11 +53,12 @@ GCJ which should work out-of-the-box. Lo
</th>
</tr>
</table>
-<br>
+<br />
+<p>
The latest development sources are available both as periodic
snapshots, and directly from the cvs source repository.
-
+</p>
<p>
Please note that the current development source tree may occasionally have
bugs which prevent it from compiling or running; however, when these problems
@@ -61,38 +66,43 @@ occur we try to fix them immediately. Pl
<a href="http://gcc.gnu.org/cgi-bin/gnatsweb.pl?user=guest&password=guest&database=gcc&cmd=login";>submit a problem report</a> if you are
using the development sources and run into such a problem.
If you are going to build from source you want to read the
-<a href=faq.html#3_0>Build Issues FAQ</a>.
+<a href="faq.html#3_0">Build Issues FAQ</a>.
+</p>
<h3>Snapshots</h3>
+<p>
Snapshots of the current CVS tree are made about once a week. They are
available from <a href="http://gcc.gnu.org/snapshots.html";>
http://gcc.gnu.org/snapshots.html</a>.
-<p>
+</p>
-<h3><a name=cvs>cvs</a></h3>
+<h3><a name="cvs">cvs</a></h3>
The easiest way to get GCJ (and keep it up to date) is to check it out from
the GCC cvs repository. Follow the links below for instructions:
<ul>
-<li><A HREF="http://gcc.gnu.org/cvs.html";>read-only (anonymous) CVS access</A></li>
-<li><A HREF="http://gcc.gnu.org/cvswrite.html";>read-write CVS access</A></li>
+<li><a href="http://gcc.gnu.org/cvs.html";>read-only (anonymous) CVS access</a></li>
+<li><a href="http://gcc.gnu.org/cvswrite.html";>read-write CVS access</a></li>
</ul>
<h3>cvsweb</h3>
+<p>
You can also view the libgcj component cvs archive: the
-<A HREF="http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/boehm-gc/";>boehm-gc</A>,
-<A HREF="http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libffi/";>libffi</A>,
-<A HREF="http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libjava/";>libjava</A>,
-and <A HREF="http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/fastjar/";>fastjar</A>.
+<a href="http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/boehm-gc/";>boehm-gc</a>,
+<a href="http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libffi/";>libffi</a>,
+<a href="http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libjava/";>libjava</a>,
+and <a href="http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/fastjar/";>fastjar</a>.
+</p>
<p>
Here's the Java front end <a
href="http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/java/";>cvs
archive</a> (the entire compiler is also
<a href="http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/";>available</a>.)
+</p>
-</GCJNAV>
+</gcjnav>
</body>
</html>
Index: java/gcj2.html
===================================================================
RCS file: /cvsroot/gcc/wwwdocs/htdocs/java/gcj2.html,v
retrieving revision 1.8
diff -u -3 -p -r1.8 gcj2.html
--- java/gcj2.html 8 Feb 2001 17:48:29 -0000 1.8
+++ java/gcj2.html 23 Mar 2002 22:05:13 -0000
@@ -6,7 +6,7 @@
<body>
-<h2 align=center>The GCJ home page</h2>
+<h1>The GCJ home page</h1>
<h2>What is it?</h2>
@@ -14,12 +14,12 @@
compile both Java<sup><a href="#javatm">tm</a></sup> source and
bytecode files. The compiler can also generate class files. This new
front end is integrated into the <a
-href="http://gcc.gnu.org/";>GCC</a> project.
+href="http://gcc.gnu.org/";>GCC</a> project.</p>
<h2>What you get</h2>
-<p>The currently available code consists of several programs:
+<p>The currently available code consists of several programs:</p>
<dl>
@@ -63,11 +63,11 @@ href="http://gcc.gnu.org/";>GCC</a> proje
href="libgcj2.html">the libgcj page</a> for details on the runtime.
Note that you'll want to configure GCC to build libjava; see
<a href="build-snapshot.html">configuration and build instructions
- for GCJ</a>.
+ for GCJ</a>.</p>
<p>There are also <a href="compile.html">more detailed
- instructions</a> on compiling Java programs.
+ instructions</a> on compiling Java programs.</p>
<h2>How to get it</h2>
@@ -76,20 +76,20 @@ it is it fully integrated into GCC, you
href="http://gcc.gnu.org/cvs.html";>GCC download and build
instructions</a>. Note that you'll want to configure GCC to use the
appropriate threads system; see <a
-href="libgcj2.html">the libgcj page</a> for details.
+href="libgcj2.html">the libgcj page</a> for details.</p>
<h2>How to try it</h2>
<p>Once you've downloaded and installed gcj and libgcj, it is very
-easy to try a small Java program of your own:
+easy to try a small Java program of your own:</p>
<pre>
gcj --main=HelloWorld -o HelloWorld HelloWorld.java
./HelloWorld
</pre>
-<p><a href=""><b>Return to main page</b></a>
-<hr>
+<p><a href=""><b>Return to main page</b></a></p>
+<hr />
<blockquote>
<a name="javatm">Java</a> and all Java-based marks are trademarks or
Index: java/gcj-3.1-status.html
===================================================================
RCS file: /cvsroot/gcc/wwwdocs/htdocs/java/gcj-3.1-status.html,v
retrieving revision 1.15
diff -u -3 -p -r1.15 gcj-3.1-status.html
--- java/gcj-3.1-status.html 21 Mar 2002 17:24:33 -0000 1.15
+++ java/gcj-3.1-status.html 23 Mar 2002 22:05:13 -0000
@@ -1,5 +1,7 @@
+<html>
+
<head>
-<title> gcj 3.1 status </title
+<title> gcj 3.1 status </title>
</head>
<body bgcolor="#fffffff">
@@ -7,11 +9,11 @@
<h2> Bugs </h2>
-<table border=1 width="100%">
+<table border="1" width="100%">
<tr><th> Issue </th> <th> Status </th> <th> Who </th> </tr>
-<tr bgcolor='#eeaaaa'> <td> <a href="http://gcc.gnu.org/cgi-bin/gnatsweb.pl?database=gcc&cmd=view&pr=4715";>4715</a> </td>
+<tr bgcolor='#eeaaaa'> <td> <a href="http://gcc.gnu.org/cgi-bin/gnatsweb.pl?database=gcc&cmd=view&pr=4715";>4715</a> </td>
<td> Tree check failure in check_inner_circular_reference.
Prevents Classpath from building. Regression from 3.0.4.
Patch in PR; Alex says it causes failures
@@ -19,7 +21,7 @@
<td> Alex </td>
</tr>
-<tr> <td> <a href="http://gcc.gnu.org/cgi-bin/gnatsweb.pl?database=gcc&cmd=view&pr=5942";>5942</a> </td>
+<tr> <td> <a href="http://gcc.gnu.org/cgi-bin/gnatsweb.pl?database=gcc&cmd=view&pr=5942";>5942</a> </td>
<td> Classpath build failure </td>
<td> Alex </td>
</tr>
@@ -29,7 +31,7 @@
<h2> Platforms </h2>
-<table border=1 width="100%">
+<table border="1" width="100%">
<tr><th> Platform </th> <th> Status </th> <th> Who </th> </tr>
@@ -100,7 +102,7 @@
<tr bgcolor="#eeaaaa"> <td>alpha-dec-osf4.0f</td>
<td> <a
- href=""http://gcc.gnu.org/ml/gcc-testresults/2002-03/msg00478.html>Many
+ href="http://gcc.gnu.org/ml/gcc-testresults/2002-03/msg00478.html";>Many
regression failures</a> </td>
<td> Unknown </td>
</tr>
@@ -119,7 +121,7 @@
<h2> Packages </h2>
-<table border=1 width="100%">
+<table border="1" width="100%">
<tr><th> Package </th> <th> Status </th> <th> Who </th> </tr>
@@ -141,3 +143,5 @@
</table>
</body>
+
+</html>
Index: java/gdb.html
===================================================================
RCS file: /cvsroot/gcc/wwwdocs/htdocs/java/gdb.html,v
retrieving revision 1.6
diff -u -3 -p -r1.6 gdb.html
--- java/gdb.html 19 Apr 2001 03:57:19 -0000 1.6
+++ java/gdb.html 23 Mar 2002 22:05:13 -0000
@@ -4,8 +4,7 @@
</head>
<body>
-<p>
-<h2 align=center>Java Debugging with <tt>gdb</tt></h2>
+<h1>Java Debugging with <tt>gdb</tt></h1>
<p>
It is possible to debug Java programs compiled with GCJ using GDB.
@@ -14,56 +13,71 @@ is recommended: GDB 5.0 and earlier are
generated by GCC 3.x's new C++/Java ABI. Alternatively, it should also be
possible to rebuild GDB 5.0 with an updated libiberty directory. GDB 5.1 will
include support for the new ABI.
+</p>
<p>
When debugging GCJ-compiled Java programs, you may need to
tell GDB to ignore the <tt>SIGPWR</tt> and <tt>SIGXCPU</tt> signals
(which are used by the garbage collector). This can be done with the
GDB commands:
+</p>
<blockquote>
<tt>
-handle SIGPWR nostop noprint<br>
-handle SIGXCPU nostop noprint<br>
+handle SIGPWR nostop noprint<br />
+handle SIGXCPU nostop noprint<br />
</tt>
</blockquote>
+<p>
Alternately you can place these two lines in the file <tt>.gdbinit</tt>
in $HOME or the directory where you're running GDB.
+</p>
<p>
Remember that some optimizations performed by the compiler can make debugging
results unpredictable. When debugging libgcj itself, it is often useful to
build a non-optimized library by using `make GCJFLAGS="-g"'.
+</p>
<p>
Here is an example of debugging a simple test program (which uses multiple
Java threads) in GDB:
+</p>
-<p>
<blockquote>
<tt>
-$ <b>javac TestT.java</b><br>
-$ <b>gcj -g --main=TestT -o TestT TestT.class</b><br>
-$ <b>gdb TestT</b><br>
-GNU gdb 4.18<br>
-Copyright 1998 Free Software Foundation, Inc.<br>
-GDB is free software, covered by the GNU General Public License, and you are<br>
-welcome to change it and/or distribute copies of it under certain conditions.<br>
-Type "show copying" to see the conditions.<br>
-There is absolutely no warranty for GDB. Type "show warranty" for details.<br>
-This GDB was configured as "i386-redhat-linux"...<br>
-(gdb) <b>handle SIGPWR nostop noprint</b><br>
+$ <b>javac TestT.java</b><br />
+$ <b>gcj -g --main=TestT -o TestT TestT.class</b><br />
+$ <b>gdb TestT</b><br />
+GNU gdb 4.18<br />
+Copyright 1998 Free Software Foundation, Inc.<br />
+GDB is free software, covered by the GNU General Public License, and you are<br />
+welcome to change it and/or distribute copies of it under certain conditions.<br />
+Type "show copying" to see the conditions.<br />
+There is absolutely no warranty for GDB. Type "show warranty" for details.<br />
+This GDB was configured as "i386-redhat-linux"...<br />
+(gdb) <b>handle SIGPWR nostop noprint</b><br />
+</tt>
+</blockquote>
<pre>
Signal Stop Print Pass to program Description
SIGPWR No No Yes Power fail/restart
</pre>
-(gdb) <b>handle SIGXCPU nostop noprint</b><br>
+<blockquote>
+<tt>
+(gdb) <b>handle SIGXCPU nostop noprint</b><br />
+</tt>
+</blockquote>
<pre>
Signal Stop Print Pass to program Description
SIGXCPU No No Yes CPU time limit exceeded
</pre>
-(gdb) <b>break TestT.main</b><br>
-Breakpoint 1 at 0x8049fa2: file TestT.java, line 64.<br>
-(gdb) <b>run</b><br>
+<blockquote>
+<tt>
+(gdb) <b>break TestT.main</b><br />
+Breakpoint 1 at 0x8049fa2: file TestT.java, line 64.<br />
+(gdb) <b>run</b><br />
+</tt>
+</blockquote>
<pre>
Starting program: /disks/now/grad/mdw/src/ninja/test/mdw/TestT
[New Thread 16843 (manager thread)]
@@ -74,7 +88,11 @@ Starting program: /disks/now/grad/mdw/sr
Breakpoint 1, TestT.main (args=@806cff0) at TestT.java:64
64 TestT a1 = new TestT(1,false);
</pre>
-(gdb) <b>where</b><br>
+<blockquote>
+<tt>
+(gdb) <b>where</b><br />
+</tt>
+</blockquote>
<pre>
(gdb) where
#0 TestT.main (args=@806cff0) at TestT.java:64
@@ -90,21 +108,22 @@ Breakpoint 1, TestT.main (args=@806cff0)
at /home/cs/mdw/disks/enclave1/libgcj-991104/boehm-gc/linux_threads.c:533
#6 0x401eece9 in pthread_start_thread (arg=@bf7ffe7c) at manager.c:204
</pre>
-</tt>
-</blockquote>
<p>
Note that the stack trace includes both Java code and the native methods
in the libgcj runtime library!
+</p>
<p>
You can examine threads using the <tt>info threads</tt> and
<tt>thread</tt> commands:
+</p>
-<p>
<blockquote>
<tt>
-(gdb) <b>info threads</b><br>
+(gdb) <b>info threads</b><br />
+</tt>
+</blockquote>
<pre>
* 3 Thread 16844 TestT.main (args=@806cff0) at TestT.java:64
2 Thread 16835 (initial thread) 0x4022a1bb in __sigsuspend (set=0xbffff4f4)
@@ -112,7 +131,11 @@ You can examine threads using the <tt>in
1 Thread 16843 (manager thread) 0x402b37d0 in __poll (fds=0x808fef0,
nfds=1, timeout=2000) at ../sysdeps/unix/sysv/linux/poll.c:45
</pre>
-(gdb) <b>thread 2</b><br>
+<blockquote>
+<tt>
+(gdb) <b>thread 2</b><br />
+</tt>
+</blockquote>
<pre>
[Switching to thread 2 (Thread 16835 (initial thread))]
#0 0x4022a1bb in __sigsuspend (set=0xbffff4f4)
@@ -120,11 +143,13 @@ You can examine threads using the <tt>in
48 ../sysdeps/unix/sysv/linux/sigsuspend.c: No such file or directory.
Current language: auto; currently c
</pre>
+<blockquote>
+<tt>
(gdb)
</tt>
</blockquote>
-<hr>
+<hr />
<address>
Page written by
<a href="mailto:mdw@cs.berkeley.edu";>Matt Welsh</a>
Index: java/index.html
===================================================================
RCS file: /cvsroot/gcc/wwwdocs/htdocs/java/index.html,v
retrieving revision 1.101
diff -u -3 -p -r1.101 index.html
--- java/index.html 15 Mar 2002 20:34:48 -0000 1.101
+++ java/index.html 23 Mar 2002 22:05:13 -0000
@@ -1,10 +1,12 @@
<html>
+<head>
<title>GCJ: The GNU Compiler for Java: Home Page</title>
-<body bgcolor="white">
+</head>
+<body>
-<GCJNAV>
+<gcjnav>
-<br>
+<br />
<h1>The GNU Compiler for the Java<sup><a href="tm.html"><small>tm</small></a></sup> Programming Language</h1>
<table border="0" cellpadding="4" width="95%">
@@ -14,13 +16,13 @@
</th>
</tr>
</table>
-<br>
+<br />
GCJ is a portable, optimizing, ahead-of-time compiler for the Java
Programming Language. It can compile:
<ul>
-<li>Java source code directly to native machine code,
-<li>Java source code to Java bytecode (class files),
-<li>and Java bytecode to native machine code.
+<li>Java source code directly to native machine code,</li>
+<li>Java source code to Java bytecode (class files),</li>
+<li>and Java bytecode to native machine code.</li>
</ul>
Compiled applications are linked with the GCJ runtime,
@@ -30,34 +32,34 @@ dynamically load and interpret class fil
compiled/interpreted applications.
<p>
-
Most of the APIs specified by "The Java Class Libraries" Second
Edition and the "Java 2 Platform supplement" are supported, including
collections, networking, reflection, and serialization. AWT is
currently unsupported, but work to implement it is in progress.
+</p>
<p>
-
Debugging is supported using recent versions of the
GNU debugger, <a href="http://sources.redhat.com/gdb/";>GDB</a>.
A <a href="gdb.html">short tutorial</a> on using GDB to debug
GCJ-compiled applications is available.
+</p>
<p>
-
In addition to regular native programming, GCJ can be configured as a
cross-compiler, suitable for embedded systems programming.
+</p>
<p>
-
-GCJ is part of the GNU Compiler Collection (<A HREF="../">GCC</A>). GCC,
+GCJ is part of the GNU Compiler Collection (<a href="../">GCC</a>). GCC,
GDB and related tools are
<a href="http://www.gnu.org/philosophy/free-sw.html";>Free Software</a>.
libgcj is slowly being merged with <a
href="http://www.gnu.org/software/classpath/";>GNU Classpath</a>. (You
can see the <a href="libgcj-classpath-compare.html">status of the merge</a>.)
-<br>
-<br>
+</p>
+<br />
+<br />
<table border="0" cellpadding="4" width="95%">
<tr bgcolor="#b0d0ff">
@@ -80,7 +82,7 @@ to disable assignability checks for stor
code that is known not to throw <code>ArrayStoreException</code>, this
flag can be used to disable the check operations. In which case it can
provide a reasonable performance boost and slight code size reduction.
-</td><tr>
+</td></tr>
<tr><td valign="top">
<b>January 22, 2002</b>
@@ -165,9 +167,9 @@ contribution.
<tr><td valign="top">
<b>June 18, 2001</b>
</td><td>
-<B>GCC 3.0 has been released!</B> Everything you need to build and run GCJ is now
+<b>GCC 3.0 has been released!</b> Everything you need to build and run GCJ is now
included in a single source distribution. Download it from one of our
-<A HREF="../mirrors.html">mirror sites</A>.
+<a href="../mirrors.html">mirror sites</a>.
</td></tr>
<tr><td valign="top">
@@ -198,7 +200,7 @@ Currently, this code is enabled for IA-6
</table>
-</GCJNAV>
+</gcjnav>
</body>
</html>
Index: java/libgcj2.html
===================================================================
RCS file: /cvsroot/gcc/wwwdocs/htdocs/java/libgcj2.html,v
retrieving revision 1.7
diff -u -3 -p -r1.7 libgcj2.html
--- java/libgcj2.html 17 Feb 2001 10:04:25 -0000 1.7
+++ java/libgcj2.html 23 Mar 2002 22:05:13 -0000
@@ -6,41 +6,41 @@
<body>
- <h2 align=center>The libgcj home page</h2>
+ <h1>The libgcj home page</h1>
<h2>What is it?</h2>
<p>``libgcj'' is the runtime that goes along with the <a
href="gcj2.html">gcj</a> front end to GCC. libgcj includes parts
of the Java Class Libraries, plus glue to connect the libraries to
- the compiler and the underlying OS.
+ the compiler and the underlying OS.</p>
<h2>What you get</h2>
<p>libgcj eventually builds a couple of libraries (one for the
runtime and one for the garbage collector), a ``zip'' version of
the class libraries, and a program called ``jv-convert'' which can
- be used to do character encoding transformations.
+ be used to do character encoding transformations.</p>
<h2>What is missing?</h2>
<p>The runtime is not yet fully complete. Parts of the standard
class libraries are missing (most notably AWT), though much of the
equivalent of JDK 1.2 has been supported.
- Also, the bytecode interpreter available only on certain platforms.
+ Also, the bytecode interpreter available only on certain platforms.</p>
<h2>How to get it</h2>
<p>Now that libgcj is part of GCC, just follow the directions for
- <a href="download.html">downloading</a> the GCJ front-end.
+ <a href="download.html">downloading</a> the GCJ front-end.</p>
<h2>How to build it</h2>
<p>Just follow the directions for
- <a href="build-snapshot.html"> building</a> GCJ.
+ <a href="build-snapshot.html"> building</a> GCJ.</p>
<p>There are a few options you might consider passing to
- ``configure'':
+ ``configure'':</p>
<dl>
<dt>--enable-java-gc=TYPE</dt>
@@ -63,7 +63,7 @@
</dl>
-<hr>
+<hr />
<a href="index.html">Back to main page</a>
Index: java/libgcj-classpath-compare.html
===================================================================
RCS file: /cvsroot/gcc/wwwdocs/htdocs/java/libgcj-classpath-compare.html,v
retrieving revision 1.36
diff -u -3 -p -r1.36 libgcj-classpath-compare.html
--- java/libgcj-classpath-compare.html 17 Feb 2002 23:49:59 -0000 1.36
+++ java/libgcj-classpath-compare.html 23 Mar 2002 22:05:14 -0000
@@ -17,7 +17,7 @@ has been reintroduced. <em>Note that su
automatically merged.</em> Any merging must be done manually; some
differences are currently required.</p>
-<table border=1 width="100%">
+<table border="1" width="100%">
<tr><th>Class</th> <th>libgcj</th> <th>Classpath</th> <th>Merge Status</th> </tr>
<tr> <td>java.awt.Polygon</td> <td>Yes</td> <td>Yes</td> <td bgcolor="#eeeeaa">No</td> </tr>
<tr> <td>java.awt.ScrollPane</td> <td>Yes</td> <td>Yes</td> <td bgcolor="#eeeeaa">No</td> </tr>
Index: java/libgcj-platforms.html
===================================================================
RCS file: /cvsroot/gcc/wwwdocs/htdocs/java/libgcj-platforms.html,v
retrieving revision 1.20
diff -u -3 -p -r1.20 libgcj-platforms.html
--- java/libgcj-platforms.html 15 Aug 2001 16:06:13 -0000 1.20
+++ java/libgcj-platforms.html 23 Mar 2002 22:05:14 -0000
@@ -11,24 +11,24 @@
<h2> Platform Coverage </h2>
<p>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 want to compare results against a known building platform, i686-pc-linux-gnu.</p>
<p>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.
+a choice of platforms to build upon.</p>
<p>Please send build/test results (in the format described below) to
<a href="mailto:java@gcc.gnu.org";>java@gcc.gnu.org</a>.
-<br>You may also address questions to
+<br />You may also address questions to
<a href="mailto:java@gcc.gnu.org";>java-discuss</a>
or to indicate that you would like to help in another way with some phase of the
-libgcj-2.95 release cycle.
+libgcj-2.95 release cycle.</p>
<h2>How to run the tests</h2>
<p> First, you must have built and installed
<a href="libgcj.html">libgcj</a> using the
-<b>libgcj-2_95-branch</b> branch of the source.
+<b>libgcj-2_95-branch</b> branch of the source.</p>
<p>This can be done by including the <tt>'-rlibgcj-2_95-branch'</tt>
flag on the <tt>'cvs co'</tt> command line or downloading the
<a href="ftp://sources.redhat.com/pub/java/snapshots/";>snapshot</a>
@@ -39,19 +39,19 @@ build instructions on the libgcj page</a
the snapshoting process has been temporarily changed to use the
<tt>libgcj-2_95-branch</tt> 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).
+to the main source tree but not to the branch).</p>
<p> Next, go to the <tt>libjava/testsuite</tt> directory of your build
-tree and run <tt>'make check'</tt> after doing the following:
+tree and run <tt>'make check'</tt> after doing the following:</p>
<ul>
<li>In order to more fully exercise libgcj, it is highly recommended to
include the
<a href="http://sources.redhat.com/mauve/";>Mauve testsuite</a>
in the test run.
- <br>The Mauve tests are available for
+ <br />The Mauve tests are available for
<a href="http://sources.redhat.com/mauve/download.html";>download</a>
- via both anonymous cvs and snapshots.
- <li>The env variable MAUVEDIR must be set to the top of the Mauve source tree
+ via both anonymous cvs and snapshots.</li>
+ <li>The env variable MAUVEDIR must be set to the top of the Mauve source tree.</li>
<li>The testsuites rely on the dejagnu package. You can download the
<a href="ftp://gcc.gnu.org/pub/gcc/infrastructure/dejagnu-19990614.tar.gz";>current dejagnu snapshot</a>
from gcc. Please note that some earlier versions of dejagnu are missing a
@@ -59,18 +59,18 @@ tree and run <tt>'make check'</tt> after
running the testsuites with the current snapshot of dejagnu before reporting
any testsuite platform problems. There is a short entry in the
<a href="http://gcc.gnu.org/faq.html#dejagnu";>gcc FAQ</a>
- if you would like more information about this issue.
+ if you would like more information about this issue.</li>
</ul>
<h2>Testing notes</h2>
<ul>
<li>By default, tests that first compile to bytecode use an installed
<tt>javac</tt> program. Set the environment variable <tt>JAVAC</tt>
- to <tt>'gcj -C'</tt> to use the installed gcj for this purpose.
+ to <tt>'gcj -C'</tt> to use the installed gcj for this purpose.</li>
<li> 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.
+ to get certain java/net Mauve tests to execute.</li>
<li>An gcc patch affecting <tt>gcj</tt> was made on 24-June-99.
Developers using cvs to access the gcc source should update an rebuild
to get that fix. The next
@@ -85,13 +85,13 @@ tree and run <tt>'make check'</tt> after
GCJ_UNDER_TEST='gcj -L/x2/java/install/lib' check
</pre>
i.e. GCJ_UNDER_TEST needs a -L pointing to the libjava build directory and
- JAVAC needs a -I pointing to the zip file.
+ JAVAC needs a -I pointing to the zip file.</li>
</ul>
<h2>Current Platform Testing Status</h2>
<p>This is the current results for the platforms reported to us. Please use
this format when reporting your results.
-<p>
+</p>
<table border="2"
cellpadding="2">
<tr>
@@ -120,9 +120,9 @@ OK
</td>
<td>
# of expected passes 1876
-<br>
+<br />
# of unexpected failures 32
-<br>
+<br />
# of expected failures 6
</td>
</tr>
@@ -132,17 +132,17 @@ alphapca56-unknown-linux-gnu
</td>
<td>
--enable-threads=posix
-<br>--enable-fast-character
-<br>--enable-java-gc=boehm
+<br />--enable-fast-character
+<br />--enable-java-gc=boehm
</td>
<td>
OK
</td>
<td>
# of expected passes 187
-<br>
+<br />
# of unexpected failures 19
-<br>
+<br />
# of expected failures 18
</td>
</tr>
@@ -157,9 +157,9 @@ OK
</td>
<td>
# of expected passes 60
-<br>
+<br />
# of unexpected failures 68
-<br>
+<br />
# of expected failures 96
</td>
</tr>
@@ -175,9 +175,9 @@ OK
</td>
<td>
# of expected passes 196
-<br>
+<br />
# of unexpected failures 22
-<br>
+<br />
# of expected failures 8
</td>
</tr>
@@ -188,21 +188,21 @@ OK
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.
+it is necessary to comprehend the deviations.</p>
<p>Note that if you are not using POSIX threads, some tests will not complete
-successfully, so differences should be expected.
+successfully, so differences should be expected.</p>
<p>Please send build/test results to
<a href="mailto:java@gcc.gnu.org";>java@gcc.gnu.org</a>
-in this format.
+in this format.</p>
<h2>Submitting Patches</h2>
-<tt>libgcj-2.95</tt> should be considered frozen except for low-risk
+<p><tt>libgcj-2.95</tt> 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.
+and not the libgcj-2_95-branch.</p>
<p>The mailing list,
<a href="mailto:java-patches@gcc.gnu.org";>java-patches@gcc.gnu.org</a>
@@ -210,26 +210,26 @@ 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.
+with an explanation and a ChangeLog entry.</p>
<p>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.
+list; this can happen concurrently with the checkin.</p>
<p>Some discussion will probably take place on this list (just as with
gcc-patches). The
<a href="/java/">web page has subscription info</a>,
as well as a
<a href="http://gcc.gnu.org/ml/java-patches/";>
-link to the archives</a>.
+link to the archives</a>.</p>
<p>The
<a href="mailto:java-patches@gcc.gnu.org";>java-patches</a>
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.
+please don't send them to java-patches.</p>
</body>
</html>
Index: java/merge-status.html
===================================================================
RCS file: /cvsroot/gcc/wwwdocs/htdocs/java/merge-status.html,v
retrieving revision 1.6
diff -u -3 -p -r1.6 merge-status.html
--- java/merge-status.html 23 Mar 2001 19:46:50 -0000 1.6
+++ java/merge-status.html 23 Mar 2002 22:05:15 -0000
@@ -8,7 +8,7 @@
<h1>Classpath / libgcj merge status</h1>
-<table border=1 width="100%">
+<table border="1" width="100%">
<tr> <th width="50%">File</th> <th>Status</th> <th>Notes</th> </tr>
<tr> <td align="left">compat/java.net/GetSocketOptionInfo.java</td> <td>unmerged</td> <td></td> </tr>
@@ -184,9 +184,9 @@
<tr> <td align="left">java/beans/beancontext/BeanContextServicesListener.java</td> <td>unmerged</td> <td></td> </tr>
<tr> <td align="left">java/io/BlockDataException.java</td> <td>unmerged</td> <td></td> </tr>
<tr> <td align="left">java/io/BufferedInputStream.java</td> <td>unmerged</td> <td></td> </tr>
-<tr> <td align="left">java/io/BufferedOutputStream.java</td> <td>merged</td> <td></td> </tr>
+<tr> <td align="left"><font color="green">java/io/BufferedOutputStream.java</font></td> <td><font color="green">merged</font></td> <td></td> </tr>
<tr> <td align="left">java/io/BufferedReader.java</td> <td>unmerged</td> <td></td> </tr>
-<tr> <td align="left">java/io/BufferedWriter.java</td> <td>merged</td> <td></td> </tr>
+<tr> <td align="left"><font color="green">java/io/BufferedWriter.javad</font></td> <td><font color="green">merged</font></td> <td></td> </tr>
<tr> <td align="left">java/io/ByteArrayInputStream.java</td> <td>unmerged</td> <td></td> </tr>
<tr> <td align="left">java/io/ByteArrayOutputStream.java</td> <td>unmerged</td> <td></td> </tr>
<tr> <td align="left">java/io/CharArrayReader.java</td> <td>unmerged</td> <td></td> </tr>
@@ -234,10 +234,10 @@
<tr> <td align="left">java/io/OptionalDataException.java</td> <td>unmerged</td> <td></td> </tr>
<tr> <td align="left">java/io/OutputStream.java</td> <td>unmerged</td> <td></td> </tr>
<tr> <td align="left">java/io/OutputStreamWriter.java</td> <td>unmerged</td> <td></td> </tr>
-<tr> <td align="left">java/io/PipedInputStream.java</td> <td>merged</td> <td></td> </tr>
-<tr> <td align="left">java/io/PipedOutputStream.java</td> <td>merged</td> <td></td> </tr>
-<tr> <td align="left">java/io/PipedReader.java</td> <td>merged</td> <td></td> </tr>
-<tr> <td align="left">java/io/PipedWriter.java</td> <td>merged</td> <td></td> </tr>
+<tr> <td align="left"><font color="green">java/io/PipedInputStream.java</font></td> <td><font color="green">merged</font></td> <td></td> </tr>
+<tr> <td align="left"><font color="green">java/io/PipedOutputStream.java</font></td> <td><font color="green">merged</font></td> <td></td> </tr>
+<tr> <td align="left"><font color="green">java/io/PipedReader.java</font></td> <td><font color="green">merged</font></td> <td></td> </tr>
+<tr> <td align="left"><font color="green">java/io/PipedWriter.java</font></td> <td><font color="green">merged</font></td> <td></td> </tr>
<tr> <td align="left">java/io/PrintStream.java</td> <td>unmerged</td> <td></td> </tr>
<tr> <td align="left">java/io/PrintWriter.java</td> <td>unmerged</td> <td></td> </tr>
<tr> <td align="left">java/io/PushbackInputStream.java</td> <td>unmerged</td> <td></td> </tr>
@@ -320,12 +320,12 @@
<tr> <td align="left">java/lang/Short.java</td> <td>unmerged</td> <td></td> </tr>
<tr> <td align="left">java/lang/StackOverflowError.java</td> <td>unmerged</td> <td></td> </tr>
<tr> <td align="left">java/lang/String.java</td> <td>unmerged</td> <td></td> </tr>
-<tr> <td fgcolor="green" align="left">java/lang/StringBuffer.java</td> <td fgcolor="green">merged</td> <td></td> </tr>
+<tr> <td align="left"><font color="green">java/lang/StringBuffer.java</font></td> <td><font color="green">merged</font></td> <td></td> </tr>
<tr> <td align="left">java/lang/StringIndexOutOfBoundsException.java</td> <td>unmerged</td> <td></td> </tr>
<tr> <td align="left">java/lang/System.java</td> <td>unmerged</td> <td></td> </tr>
<tr> <td align="left">java/lang/Thread.java</td> <td>unmerged</td> <td></td> </tr>
<tr> <td align="left">java/lang/ThreadDeath.java</td> <td>unmerged</td> <td></td> </tr>
-<tr> <td fgcolor="green" align="left">java/lang/ThreadGroup.java</td> <td fgcolor="green">merged</td> <td></td> </tr>
+<tr> <td align="left"><font color="green">java/lang/ThreadGroup.java</font></td> <td><font color="green">merged</font></td> <td></td> </tr>
<tr> <td align="left">java/lang/Throwable.java</td> <td>unmerged</td> <td></td> </tr>
<tr> <td align="left">java/lang/UnknownError.java</td> <td>unmerged</td> <td></td> </tr>
<tr> <td align="left">java/lang/UnsatisfiedLinkError.java</td> <td>unmerged</td> <td></td> </tr>
Index: java/old-news.html
===================================================================
RCS file: /cvsroot/gcc/wwwdocs/htdocs/java/old-news.html,v
retrieving revision 1.19
diff -u -3 -p -r1.19 old-news.html
--- java/old-news.html 28 Jan 2002 07:12:26 -0000 1.19
+++ java/old-news.html 23 Mar 2002 22:05:15 -0000
@@ -20,8 +20,8 @@ The new package is now JDK 1.2 compliant
<b>March 25, 2001</b>
</td><td>
It is now possible to call methods on Java interface references from C++ code
-via <A HREF="papers/cni/t1.html">CNI</A>, thanks to Bryce McKinlay's compiler
-work. <A HREF=http://gcc.gnu.org/ml/gcc-patches/2001-03/msg01483.html>Details.</A>
+via <a href="papers/cni/t1.html">CNI</a>, thanks to Bryce McKinlay's compiler
+work. <a href="http://gcc.gnu.org/ml/gcc-patches/2001-03/msg01483.html";>Details.</a>
</td></tr>
<tr><td valign="top">
@@ -46,7 +46,7 @@ find bugs!
<b>February 8, 2001</b>
</td><td>
Made use of Warren Levy's change to the
-<A HREF="http://sources.redhat.com/mauve/";>Mauve test suite</A> to handle
+<a href="http://sources.redhat.com/mauve/";>Mauve test suite</a> to handle
regressions.
Modifications have been made to <tt>mauve.exp</tt> to copy the newly created
<tt>xfails</tt> file of known library failures from the source tree
@@ -54,9 +54,9 @@ to the directory where the libjava <tt>'
This allows the testsuite to ignore <tt>XFAIL</tt>s and thus highlight
true regressions in the library. The Mauve tests are
<a href="test.html">automatically run</a> as part of a libjava
-<TT>'make check'</TT> as long as the Mauve suite is accessible
-and the env var <TT>MAUVEDIR</TT> is set to point to the top-level
-of the <A HREF="http://sources.redhat.com/mauve/download.html";>Mauve source</A>.
+<tt>'make check'</tt> as long as the Mauve suite is accessible
+and the env var <tt>MAUVEDIR</tt> is set to point to the top-level
+of the <a href="http://sources.redhat.com/mauve/download.html";>Mauve source</a>.
</td></tr>
<tr><td valign="top">
@@ -94,20 +94,20 @@ Thanks to Richard Henderson's recent <co
<tr><td valign="top">
<b>December 9, 2000</b>
</td><td>
-The libgcj sources have <A HREF="http://gcc.gnu.org/ml/java/2000-12/msg00102.html";>
-migrated</A> to the gcc repository. We've imported
-<A HREF="http://sourceforge.net/projects/fastjar";>fastjar</A> in our
-<A HREF="http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/fastjar/";>tree</A>
+The libgcj sources have <a href="http://gcc.gnu.org/ml/java/2000-12/msg00102.html";>
+migrated</a> to the gcc repository. We've imported
+<a href="http://sourceforge.net/projects/fastjar";>fastjar</a> in our
+<a href="http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/fastjar/";>tree</a>
and use it as a replacement to zip. </td></tr>
<tr><td valign="top">
<b>December 8, 2000</b>
</td><td>
-The libgcj repository is now <A HREF="http://gcc.gnu.org/ml/java/2000-12/msg00095.html";>
-closed</A>: We're moving our sources over to the gcc
-<A HREF="http://gcc.gnu.org/ml/java-announce/2000/msg00003.html";>
-tree</A>. Read <A HREF="http://gcc.gnu.org/cvs.html";>here</A> and
-<A HREF="http://gcc.gnu.org/cvswrite.html";>here</A> how you will soon check
+The libgcj repository is now <a href="http://gcc.gnu.org/ml/java/2000-12/msg00095.html";>
+closed</a>: We're moving our sources over to the gcc
+<a href="http://gcc.gnu.org/ml/java-announce/2000/msg00003.html";>
+tree</a>. Read <a href="http://gcc.gnu.org/cvs.html";>here</a> and
+<a href="http://gcc.gnu.org/cvswrite.html";>here</a> how you will soon check
your sources out.
</td></tr>
@@ -154,8 +154,8 @@ also been working on AWT.
Bryce McKinlay checked in a patch that enables bitmap-descriptor based
marking in the garbage collector. This code includes work by
Tom Tromey and Hans Boehm, and results in some significant
-<A HREF="http://gcc.gnu.org/ml/java-patches/2000-q3/msg00161.html";>
-performance gains</A> in memory-intensive code.
+<a href="http://gcc.gnu.org/ml/java-patches/2000-q3/msg00161.html";>
+performance gains</a> in memory-intensive code.
</td></tr>
<tr><td valign="top">
@@ -198,9 +198,9 @@ gcj.
<tr><td valign="top">
<b>June 27, 2000</b>
</td><td>
-A new <A HREF="done.html">Done with GCJ</A> section was added.
-Send your GCJ stories <A HREF="mailto:java@gcc.gnu.org";>
-here</A>.
+A new <a href="done.html">Done with GCJ</a> section was added.
+Send your GCJ stories <a href="mailto:java@gcc.gnu.org";>
+here</a>.
</td></tr>
<tr><td valign="top">
@@ -208,11 +208,11 @@ here</A>.
</td><td>
Today we merged some major work done at Red Hat. This included:
<ul>
-<li> Substantial work for the IA-64 port.
-<li> <code>java.beans</code> from <a href="http://www.gnu.org/software/classpath/";>Classpath</a>.
+<li> Substantial work for the IA-64 port.</li>
+<li> <code>java.beans</code> from <a href="http://www.gnu.org/software/classpath/";>Classpath</a>.</li>
<li> A somewhat modified initial implementation of serialization.
- (This is known not to interoperate with other implementations yet.)
-<li> Miscellaneous bug fixes.
+ (This is known not to interoperate with other implementations yet.)</li>
+<li> Miscellaneous bug fixes.</li>
</ul>
</td></tr>
Index: java/port-files.html
===================================================================
RCS file: /cvsroot/gcc/wwwdocs/htdocs/java/port-files.html,v
retrieving revision 1.3
diff -u -3 -p -r1.3 port-files.html
--- java/port-files.html 16 Mar 2001 15:20:44 -0000 1.3
+++ java/port-files.html 23 Mar 2002 22:05:15 -0000
@@ -9,83 +9,95 @@
<h2>Introduction</h2>
-The classes in <tt>java.io</tt> ultimately require some connection to
+<p>The classes in <tt>java.io</tt> ultimately require some connection to
the underlying operating system's notion of files. This document
-attempts to decribe how to port the native file-handling layer.<p>
+attempts to decribe how to port the native file-handling layer.</p>
-There are basically two parts to the porting. First, the
+<p>There are basically two parts to the porting. First, the
<tt>FileDescriptor</tt> class is used to represent an open file. It
has native methods to open, close, read, write, etc. Second, the
<tt>File</tt> class can be used to manipulate the file system via
-methods such as mkdir, rename, etc.<p>
+methods such as mkdir, rename, etc.</p>
<h2>Porting <tt>FileDescriptor</tt></h2>
-The current implementation of <tt>FileDescriptor</tt> assumes a
+<p>The current implementation of <tt>FileDescriptor</tt> assumes a
POSIX-like system. For instance, the current representation of the
-native state is a single <tt>int</tt>, the POSIX file descriptor.<p>
+native state is a single <tt>int</tt>, the POSIX file descriptor.</p>
Here are the semantics of the various functions you must write to port
this class:
<dl>
-<dt>boolean valid ()
+<dt>boolean valid ()</dt>
<dd>Should return <tt>true</tt> if this object is valid, and
<tt>false</tt> otherwise.
+</dd>
-<dt>void sync ()
+<dt>void sync ()</dt>
<dd>Synchronize the file descriptor. On error, throw a
<tt>SyncFailedException</tt>.
+</dd>
-<dt>int open (String path, int flags)
+<dt>int open (String path, int flags)</dt>
<dd>Open a file and return the native file descriptor. Should throw
exception on error. <tt>flags</tt> is either <tt>READ</tt>,
<tt>WRITE</tt>, <tt>READ | WRITE</tt>, or <tt>WRITE | APPEND</tt> and
is used to specify the mode in which the file should be opened.
+</dd>
-<dt>void write (int byte)
+<dt>void write (int byte)</dt>
<dd>Write a single byte (low-order bits of <tt>byte</tt>) to the
file. Throw exception on error.
+</dd>
-<dt>void write (byte[] bytes, int offset, int length)
+<dt>void write (byte[] bytes, int offset, int length)</dt>
<dd>Write several bytes to the file. If <tt>bytes</tt> is null, throw
<tt>NullPointerException</tt>. Should check offset and length as
well, and throw <tt>ArrayIndexOutOfBoundsException</tt> on error.
Also should throw exception if write fails.
+</dd>
-<dt>void close ()
+<dt>void close ()</dt>
<dd>Close the file. Throw exception on error.
+</dd>
-<dt>int seek (long pos, int whence)
+<dt>int seek (long pos, int whence)</dt>
<dd>Seek to a new position in the file. <tt>whence</tt> is either
<tt>SET</tt> (set the new position absolutely) or <tt>CUR</tt> (set
the new position relative to the current position. If the call would
set the position past the end of the file, should throw
<tt>EOFException</tt> Should throw exception on error. Return value
is the new position.
+</dd>
-<dt>long length ()
+<dt>long length ()</dt>
<dd>Returns the size of the file in bytes. Throws exception on error.
+</dd>
-<dt>long getFilePointer ()
+<dt>long getFilePointer ()</dt>
<dd>Returns current location in file of file pointer. Throws
exception on error.
+</dd>
-<dt>int read ()
+<dt>int read ()</dt>
<dd>Read a single byte from the file. On EOF, return -1. On error,
throw exception.
+</dd>
-<dt>int read (byte[] buffer, int offset, int count)
+<dt>int read (byte[] buffer, int offset, int count)</dt>
<dd>First, check buffer, offset, and count, just like <tt>write</tt>.
Then read as many bytes are as available into buffer (at location
offset), up to count bytes. If EOF hit before any bytes read, return
-1. On error, throw exception. Otherwise, return number of bytes
read. This method should never return 0; instead it should block
until at least one byte is read.
+</dd>
-<dt>int available ()
+<dt>int available ()</dt>
<dd>Return number of bytes that could be read without blocking. On
error, throw exception.
+</dd>
</dl>
@@ -96,54 +108,63 @@ to manipulating the file system. It is
are primarily concerned with. Here are the methods involved:
<dl>
-<dt>boolean access (String canonical, int query)
+<dt>boolean access (String canonical, int query)</dt>
<dd>Determine if access to the file is permitted. <tt>canonical</tt>
is the file name to use. <tt>query</tt> is <tt>READ</tt> to see if
read access is permitted, <tt>WRITE</tt> to see if write access is
permitted, and <tt>EXISTS</tt> to see if the file exists. canonical
might be null, in which case the answer should be false.
+</dd>
-<dt>boolean stat (String canonical, int query)
+<dt>boolean stat (String canonical, int query)</dt>
<dd>Like <tt>access</tt>, but used to query file type. In this case,
<tt>query</tt> is either <tt>DIRECTORY</tt> to see if the name
represents a directory, or <tt>ISFILE</tt> to see if the name
represents a file (which is basically anything that is not a
directory).
+</dd>
-<dt>long attr (String canonical, int query)
+<dt>long attr (String canonical, int query)</dt>
<dd>Like <tt>stat</tt>, but returns non-boolean information about the
file. If <tt>query</tt> is <tt>MODIFIED</tt>, return the last
modified time (in milliseconds since the Epoch). If it is
<tt>LENGTH</tt>, return the file's length. Return 0 on error.
+</dd>
-<dt>String getCanonicalPath ()
+<dt>String getCanonicalPath ()</dt>
<dd>Return the canonical form of <tt>this.path</tt>. Throw exception
on error. See the JCL book for information on path canonicalization.
+</dd>
-<dt>boolean isAbsolute ()
+<dt>boolean isAbsolute ()</dt>
<dd>Return true if <tt>this.path</tt> represents an absolute path for
the underlying filesystem. The current implementation knows about
both POSIX and Windows filesystems, so probably should not need much
porting.
+</dd>
-<dt>String[] performList (jstring canon, FilenameFilter filter)
+<dt>String[] performList (jstring canon, FilenameFilter filter)</dt>
<dd>If the string is null, just return. Otherwise, if it names a
directory, this should return an array of all the files in the
directory. The directories ``.'' and ``..'' should be omitted. If
the path is not a directory, this method should return null.
+</dd>
-<dt>boolean performMkdir ()
+<dt>boolean performMkdir ()</dt>
<dd>This function should make a directory named by <tt>path</tt>.
Returns true on success.
+</dd>
-<dt>boolean performRenameTo (File dest)
+<dt>boolean performRenameTo (File dest)</dt>
<dd>This function should rename the current file to <tt>dest</tt>.
Returns true on success.
+</dd>
-<dt>boolean performDelete (String canonical)
+<dt>boolean performDelete (String canonical)</dt>
<dd>Should try to delete the path specified by <tt>canonical</tt>.
This might be either a file or a directory. Should return true on
success.
+</dd>
</dl>
</body>
Index: java/port-signals.html
===================================================================
RCS file: /cvsroot/gcc/wwwdocs/htdocs/java/port-signals.html,v
retrieving revision 1.4
diff -u -3 -p -r1.4 port-signals.html
--- java/port-signals.html 16 Mar 2001 15:20:44 -0000 1.4
+++ java/port-signals.html 23 Mar 2002 22:05:15 -0000
@@ -9,68 +9,68 @@
<h2>Introduction</h2>
-When a signal is sent to a Java program, the Java runtime code should
+<p>When a signal is sent to a Java program, the Java runtime code should
raise an exception which can be caught by Java application code.
Examples of such signals are <tt>SIGSEGV</tt> (segment violation) and
<tt>SIGFPE</tt> (arithmetic exception). It is not always clear which
Java exceptions should be raised, but in these cases it is fairly
obvious: <tt>NullPointerException</tt> and
-<tt>ArithmeticException</tt>. <p>
+<tt>ArithmeticException</tt>. </p>
-Unfortunately, there is no portable way to turn a signal into an
+<p>Unfortunately, there is no portable way to turn a signal into an
exception: this depends on the processor architecture and operating
system being used. As a consequence of this, some porting work may be
-necessary in order to catch signals.<p>
+necessary in order to catch signals.</p>
-The problem is that a signal handler may be called from the OS kernel
+<p>The problem is that a signal handler may be called from the OS kernel
with a stack frame which cannot be walked by signal handling code. In
order to provide <tt>throw()</tt> with a stack which it can walk, the
signal handler may need to alter the stack frame to make it
appear that the handler has been directly called from the code which
-faulted and caused the signal.<p>
+faulted and caused the signal.</p>
<h2>Details</h2>
-Firstly, you must determine the address of the instruction which
+<p>Firstly, you must determine the address of the instruction which
caused the signal to be sent: the point at which the Java program was
interrupted. There is no standard way to do this, so you will need to
read the documentation of your OS, or possibly even the kernel sources
to discover where the interrupted program counter (PC) and frame
pointer (FP) are saved. You may have to reverse engineer the kernel
trap, or use gdb to see what is on the stack at the time a signal
-handler is called.<p>
+handler is called.</p>
-Once you have done this, you'll need to write a little assembler code
+<p>Once you have done this, you'll need to write a little assembler code
to take the PC and FP at the time of call and rewrite the current
stack frame to make it appear that the signal handler was directly called from
-the faulting code.<p>
+the faulting code.</p>
-Here's an i386 Linux example of code which does this:<p>
+<p>Here's an i386 Linux example of code which does this:</p>
<pre>
#define MAKE_THROW_FRAME \
{ \
- void **_p = (void **)&_dummy; \
+ void **_p = (void **)&_dummy; \
struct sigcontext_struct *_regs = (struct sigcontext_struct *)++_p; \
\
- register unsigned long _ebp = _regs->ebp; \
- register unsigned long _eip = _regs->eip; \
+ register unsigned long _ebp = _regs->ebp; \
+ register unsigned long _eip = _regs->eip; \
\
asm volatile ("mov %0, (%%ebp); mov %1, 4(%%ebp)" \
: : "r"(_ebp), "r"(_eip)); \
}
</pre>
-Here, <tt>dummy</tt> is the <tt>int</tt> argument passed to a signal
+<p>Here, <tt>dummy</tt> is the <tt>int</tt> argument passed to a signal
handler. Immediately below this on the stack is a <tt>struct
sigcontext_struct</tt> which contains the registers at the point the
fault occurred. The assembly language instructions rewrite the
-current stack frame to point to the code which was interrupted.<p>
+current stack frame to point to the code which was interrupted.</p>
-Once you've written this code for processor <tt>foo</tt>, create a new
+<p>Once you've written this code for processor <tt>foo</tt>, create a new
<tt>foo-signal.h</tt> file and put it in the <tt>libjava/include</tt>
directory. Add a reference to <tt>foo-signal.h</tt> to the list in
-<tt>libjava/configure.in</tt>:
+<tt>libjava/configure.in</tt>:</p>
<pre>
case "${host}" in
@@ -86,11 +86,11 @@ case "${host}" in
esac
</pre>
-Specimen signal handling code for other processors is in the
-<tt>libjava/include</tt> directory.<p>
+<p>Specimen signal handling code for other processors is in the
+<tt>libjava/include</tt> directory.</p>
-The actual signal handlers are in <tt>libjava/prims.cc</tt>, and look
-like this:
+<p>The actual signal handlers are in <tt>libjava/prims.cc</tt>, and look
+like this:</p>
<pre>
static java::lang::NullPointerException *nullp;
@@ -101,10 +101,10 @@ SIGNAL_HANDLER (catch_segv)
}
</pre>
-You must ensure that the pointer to the exception has been initialized
+<p>You must ensure that the pointer to the exception has been initialized
to point to a Java exception before <tt>_Jv_Throw()</tt> is called: a
good place to do this is in <tt>JvRunMain</tt>, before the application
-is started.<p>
+is started.</p>
</body>
</html>
Index: java/port-threads.html
===================================================================
RCS file: /cvsroot/gcc/wwwdocs/htdocs/java/port-threads.html,v
retrieving revision 1.8
diff -u -3 -p -r1.8 port-threads.html
--- java/port-threads.html 15 Dec 2001 08:05:22 -0000 1.8
+++ java/port-threads.html 23 Mar 2002 22:05:15 -0000
@@ -9,119 +9,120 @@
<h2>Introduction</h2>
-The libjava threading layer was designed to expose precisely those
+<p>The libjava threading layer was designed to expose precisely those
pieces of a thread system that are required by a Java runtime. It
-also turns out to be fairly easy to port.<p>
+also turns out to be fairly easy to port.</p>
<h2>The First Step</h2>
-The first step to porting the threading layer is adding code to
+<p>The first step to porting the threading layer is adding code to
libjava/configure.in to handle the new system. This is fairly
-straightforward, so I won't go into any details here.<p>
+straightforward, so I won't go into any details here.</p>
-It might also be necessary to modify other configure scripts as well.
+<p>It might also be necessary to modify other configure scripts as well.
For instance, you might need to modify qthreads/configure so that
qthreads won't be built when the new thread system is in use. (This
is actually already done, but might need revisiting if we change
libjava/configure to automatically determine thread package based on
host. In this case, qthreads and boehm-gc must make the same
-determination.)<p>
+determination.)</p>
<h2>Porting Gcc</h2>
-Pieces of the gcc runtime code, in particular the exception handling,
+<p>Pieces of the gcc runtime code, in particular the exception handling,
need to know about the thread system that is in use, so any new thread
port for libjava must also involve adding new code to gcc. Generally
-this is much easier than writing the thread code for libjava.<p>
+this is much easier than writing the thread code for libjava.</p>
<ul>
<li>Add support to gcc/configure.in to support the new thread system.
gcc's configure script understands --enable-threads just as libjava's
does; the two must agree so that a single configure from the top level
-will succeed.
+will succeed.</li>
<li>Write a new ``gthr-PORT.h'' header file. See the existing gthr.h
-to see what must go into this file.
+to see what must go into this file.</li>
<li>Contact the gcc maintainers and try to get your patch installed.
-Allocate plenty of time for this step.
+Allocate plenty of time for this step.</li>
-<li>Update java/jvspec.c to tell it about the new thread library.
+<li>Update java/jvspec.c to tell it about the new thread library.</li>
</ul>
<h2>The Header File</h2>
-The second step is to write a header file which includes all the
+<p>The second step is to write a header file which includes all the
declarations that are required by libjava. This step is the bulk of
-the work involved.<p>
+the work involved.</p>
-This header file consists of a number of definitions and declarations.
+<p>This header file consists of a number of definitions and declarations.
At configure time, a link named ``java-threads.h'' will be created to
-point to the appropriate package-specific header.<p>
+point to the appropriate package-specific header.</p>
-The contents of this file are fixed in the sense that the list of
+<p>The contents of this file are fixed in the sense that the list of
declarations which must appear is fixed. The reason there is a
separate such header per thread system is so that each system can make
-its own decisions about which functions should be inlined.<p>
+its own decisions about which functions should be inlined.</p>
-A useful piece of information which doesn't seem to belong anywhere
+<p>A useful piece of information which doesn't seem to belong anywhere
else: in Java, a thread can be marked as a ``daemon'' thread before it
is started. The runtime exits when all non-daemon threads have
exited. The thread porting layer is responsible for handling this
-somehow.<p>
+somehow.</p>
<h3>Boilerplate</h3>
-Each thread header must contain a declaration of the type
+<p>Each thread header must contain a declaration of the type
``_Jv_ThreadStartFunc''. This typedef is the same in every thread
-package. Declare it thusly:
+package. Declare it thusly:</p>
<pre>
typedef void _Jv_ThreadStartFunc (java::lang::Thread *);
</pre>
<h3>Mutexes</h3>
-Mutexes (or "mutices" as some would have it) are one of two
+<p>Mutexes (or "mutices" as some would have it) are one of two
fundamental synchronization objects used by libjava. A mutex is a
lock that is held by a single thread. A thread can hold the same
mutex multiple times; they are reference counted. When one thread
holds a mutex, another thread attempting to grab the mutex will block
-until the mutex is free.<p>
+until the mutex is free.</p>
-Implementing mutexes requires a typedef and several functions:
+<p>Implementing mutexes requires a typedef and several functions:</p>
<dl>
-<dt>_Jv_Mutex_t
+<dt>_Jv_Mutex_t</dt>
<dd>A package-specific typedef which represents a mutex. This type
must be fully declared in the thread header, as memory allocation for
-mutexes is handled by the runtime and not by the thread layer.
+mutexes is handled by the runtime and not by the thread layer.</dd>
-<dt>void _Jv_MutexInit (_Jv_Mutex_t *mutex)
-<dd>A function to initialize a mutex.
+<dt>void _Jv_MutexInit (_Jv_Mutex_t *mutex)</dt>
+<dd>A function to initialize a mutex.</dd>
-<dt>void _Jv_MutexDestroy (_Jv_Mutex_t *mutex)
+<dt>void _Jv_MutexDestroy (_Jv_Mutex_t *mutex)</dt>
<dd>A function to destroy a mutex.. This function is optional. If
you define it, you must also define the preprocessor macro
<tt>_Jv_HaveMutexDestroy</tt>. The presence of this function incurs a
-performance penalty.
+performance penalty.</dd>
-<dt>int _Jv_MutexLock (_Jv_Mutex_t *mutex)
+<dt>int _Jv_MutexLock (_Jv_Mutex_t *mutex)</dt>
<dd>Lock the mutex. Note that Java mutexes are recursive, so this function
must maintain a lock-depth counter in the _Jv_Mutex_t if the underlying
platform's mutex is not recursive. Returns 0 on success, -1 on failure.
+</dd>
-<dt>int _Jv_MutexUnlock (_Jv_Mutex_t *mutex)
-<dd>Unlock the mutex. Returns 0 on success, -1 on failure.
+<dt>int _Jv_MutexUnlock (_Jv_Mutex_t *mutex)</dt>
+<dd>Unlock the mutex. Returns 0 on success, -1 on failure.</dd>
</dl>
<h3>Condition Variables</h3>
-Condition variables are the other synchronization primitive used by
-libjava. They are used to implement the wait and notify functions.<p>
+<p>Condition variables are the other synchronization primitive used by
+libjava. They are used to implement the wait and notify functions.</p>
-Each condition variable has an associated mutex. A thread acquires
+<p>Each condition variable has an associated mutex. A thread acquires
the mutex and then waits on the condition variable. This waiting
takes the form of an atomic release of the mutex (fully releasing it,
if it is held several times by the thread) followed by blocking. When
@@ -130,23 +131,23 @@ thread reawakens, re-acquires the mutex
state -- the lock depth counting must be handled correctly), and
returns. It's possible for several threads to wait on a condition
variable at the same time, and to all be reawakened simultaneously (of
-course, only one thread at a time can re-acquire the mutex).<p>
+course, only one thread at a time can re-acquire the mutex).</p>
-Once again, a typedef and several functions are required.
+<p>Once again, a typedef and several functions are required.</p>
<dl>
-<dt>_Jv_ConditionVariable_t
-<dd>A package-specific typedef which represents a condition variable.
+<dt>_Jv_ConditionVariable_t</dt>
+<dd>A package-specific typedef which represents a condition variable.</dd>
-<dt>void _Jv_CondInit (_Jv_ConditionVariable_t *condvar)
-<dd>Initialize a condition variable.
+<dt>void _Jv_CondInit (_Jv_ConditionVariable_t *condvar)</dt>
+<dd>Initialize a condition variable.</dd>
-<dt>void _Jv_CondDestroy (_Jv_ConditionVariable_t *condvar)
+<dt>void _Jv_CondDestroy (_Jv_ConditionVariable_t *condvar)</dt>
<dd>Destroy a condition variable. This function is optional. If you
define it, you must also define the preprocessor macro
<tt>_Jv_HaveCondDestroy</tt>. The presence of this function incurs a
-performance penalty.
+performance penalty.</dd>
-<dt>int _Jv_CondWait (_Jv_ConditionVariable_t *condvar, _Jv_Mutex_t *mutex, jlong milliseconds, jint nanoseconds)
+<dt>int _Jv_CondWait (_Jv_ConditionVariable_t *condvar, _Jv_Mutex_t *mutex, jlong milliseconds, jint nanoseconds)</dt>
<dd>Wait on the condition variable using the associated mutex. The
final arguments are a timeout; if 0 then no timeout is to be used. It
isn't necessary to implement nanosecond resolution. However, the best
@@ -158,98 +159,99 @@ done automatically by the OS thread laye
before or during the wait), _JV_INTERRUPTED should be returned. The interrupted
status flag is not cleared.
_Jv_CondWait should never throw an exception directly.
-Returns 0 if CONDVAR was signalled normally, or if the timeout expired.
+Returns 0 if CONDVAR was signalled normally, or if the timeout expired.</dd>
-<dt>int _Jv_CondNotify (_Jv_ConditionVariable_t *condvar, _Jv_Mutex_t *mutex)
+<dt>int _Jv_CondNotify (_Jv_ConditionVariable_t *condvar, _Jv_Mutex_t *mutex)</dt>
<dd>Signal the condition variable. This wakes up one thread
waiting on the variable. Returns 0 on success. Should return _JV_NOT_OWNER
-if current thread does not hold the mutex.
+if current thread does not hold the mutex.</dd>
<dt>int _Jv_CondNotifyAll (_Jv_ConditionVariable_t *condvar, _Jv_Mutex_t *mutex)
+</dt>
<dd>Wake up all threads waiting on the condition variable. Returns 0
on success. Should return _JV_NOT_OWNER if current thread does not hold the
-mutex.
+mutex.</dd>
</dl>
<h3>Everything Else</h3>
-There is one remaining typedef that must be defined:
+<p>There is one remaining typedef that must be defined:
``_Jv_Thread_t''. This is a typedef specific to the threads system
which represents the thread system's notion of a thread. Each
``java.lang.Thread'' object has an associated native thread object of
-this type.<p>
+this type.</p>
-The remaining functions have to do with thread creation and
-manipulation.<p>
+<p>The remaining functions have to do with thread creation and
+manipulation.</p>
<h4>Thread Creation and Destruction</h4>
<dl>
-<dt>void _Jv_InitThreads (void)
+<dt>void _Jv_InitThreads (void)</dt>
<dd>Initialize the thread system. This is called before any other
initialization is done. This should not be used to start
the first thread; that is handled elsewhere. This probably won't be
-needed by most thread packages.
+needed by most thread packages.</dd>
-<dt>_Jv_Thread_t * _Jv_ThreadInitData (java::lang::Thread *thread)
+<dt>_Jv_Thread_t * _Jv_ThreadInitData (java::lang::Thread *thread)</dt>
<dd>This is called when a new Java thread object is created. The
thread system should create a new thread, allocate any data needed to assist
the implementation of mutexes and condition variables, initialize it as
needed, and return a pointer to it (this pointer is opaque to generic threads
code). The thread should not be started yet -- in Java, thread creation and
-execution are separate.
+execution are separate.</dd>
-<dt>void _Jv_ThreadDestroyData (_Jv_Thread_t *data)
+<dt>void _Jv_ThreadDestroyData (_Jv_Thread_t *data)</dt>
<dd>This function should clean up and/or free any native resources allocated
for the thread in _Jv_ThreadInitData. It is called when the Java thread object
-is finalized.
+is finalized.</dd>
-<dt>void _Jv_ThreadStart (java::lang::Thread *thread, _Jv_Thread_t *data, _Jv_ThreadStartFunc *method)
+<dt>void _Jv_ThreadStart (java::lang::Thread *thread, _Jv_Thread_t *data, _Jv_ThreadStartFunc *method)</dt>
<dd>Start running the indicated thread. This function should examine
the Thread object and make use of the priority, daemon-ness, etc, if
possible. The argument ``data'' holds the data element previously
initialized with _Jv_ThreadInitData. The ``thread'' argument should
-be passed as the sole argument to ``method''.
+be passed as the sole argument to ``method''.</dd>
-<dt>void _Jv_ThreadWait (void)
-<dd>Wait for all non-daemon threads to exit.
+<dt>void _Jv_ThreadWait (void)</dt>
+<dd>Wait for all non-daemon threads to exit.</dd>
-<dt>void _Jv_ThreadRegister (_Jv_Thread_t *data)
+<dt>void _Jv_ThreadRegister (_Jv_Thread_t *data)</dt>
<dd>This is called from a newly created thread before the run() method is
invoked, or when a native thread is attached to the Java runtime via
JvAttachThread. It can be used to create and/or register thread-specific data
-to assist the implementation of _Jv_ThreadCurrent, for example.
+to assist the implementation of _Jv_ThreadCurrent, for example.</dd>
-<dt>void _Jv_ThreadUnRegister ()
+<dt>void _Jv_ThreadUnRegister ()</dt>
<dd>This is called from a thread which is about to die, because its run() method
has returned or it is being "detached" from the Java runtime. It gives the
thread layer a chance to clean up thread-specific data allocated in
_Jv_ThreadRegister. Note that the thread object may still be visible to Java,
-so _Jv_Thread_t data should only be freed by _Jv_ThreadDestroyData.
+so _Jv_Thread_t data should only be freed by _Jv_ThreadDestroyData.</dd>
</dl>
<h4>Truly Miscellaneous Functions</h4>
<dl>
-<dt>java::lang::Thread *_Jv_ThreadCurrent (void)
+<dt>java::lang::Thread *_Jv_ThreadCurrent (void)</dt>
<dd>Each thread package is required to maintain a mapping from the
current thread to the associated Java Thread object representing that
thread. Typically this is done by storing the pointer (from the
_Jv_ThreadInitData or _Jv_ThreadStart calls) to the thread object
-in thread-local storage. This function returns that object.
+in thread-local storage. This function returns that object.</dd>
-<dt>void _Jv_ThreadYield (void)
+<dt>void _Jv_ThreadYield (void)</dt>
<dd>Cause the current thread to yield. Strictly speaking this need
-not do anything.
+not do anything.</dd>
-<dt>void _Jv_ThreadSetPriority (_Jv_Thread_t *data, jint priority)
+<dt>void _Jv_ThreadSetPriority (_Jv_Thread_t *data, jint priority)</dt>
<dd>This is called when the priority of a thread is set. Priorities
are remembered and manipulated in the Thread class; this call exists
in case the underlying thread system has a useful notion of
-priorities to which Java priorities should be mapped.
+priorities to which Java priorities should be mapped.</dd>
-<dt>void _Jv_ThreadInterrupt (_Jv_Thread_t *data)
+<dt>void _Jv_ThreadInterrupt (_Jv_Thread_t *data)</dt>
<dd>This function is called by Thread.interrupt(). It should set
the interrupt_flag of the Thread object corresponding to DATA, and cause any
"slow" or "blocking" system I/O or a call to _Jv_CondWait to return immediately.
@@ -264,7 +266,7 @@ its interrupted status flag should be se
possible races in the interrupt implementation: it should not be possible for
an interrupt to be delivered to a thread immediately after it checks its
interrupted status flag but before it enters an interruptible blocking call,
-for example.
+for example.</dd>
</dl>
<h2>Unimplemented functionality</h2>
@@ -279,18 +281,18 @@ for example.
<dt>Thread.stop</dt>
<dd>These functions are unimplemented and never will be
implemented. They are deprecated in JDK 1.2. The current
- implementations simply throw an exception.
+ implementations simply throw an exception.</dd>
</dl>
<h2>Grey Areas</h2>
-There are still a few areas which have not been fully explored. This
-will change over time.
+<p>There are still a few areas which have not been fully explored. This
+will change over time.</p>
<ul>
<li>There is no documented way for the thread system and the GC to
interact. This is a historical accident, as our only GC right now
-knows about thread systems itself.
+knows about thread systems itself.</li>
</ul>
</body>
Index: java/projects.html
===================================================================
RCS file: /cvsroot/gcc/wwwdocs/htdocs/java/projects.html,v
retrieving revision 1.26
diff -u -3 -p -r1.26 projects.html
--- java/projects.html 6 Nov 2001 23:03:09 -0000 1.26
+++ java/projects.html 23 Mar 2002 22:05:15 -0000
@@ -4,12 +4,12 @@
</head>
<body bgcolor="#FFFFFF">
-<GCJNAV>
+<gcjnav>
- <br>
- <br>
- <h1>The GCJ Projects List</h1>
+<br /><br />
+<h1>The GCJ Projects List</h1>
+<p>
What follows is a list of projects that the GCJ community would love
to see someone pick up and run with. If you're interested in any of
these, be sure to send a note with your questions, ideas or intentions
@@ -18,10 +18,9 @@ href="mailto:java@gcc.gnu.org";>java-disc
mailing list. Similarly, if you would like to see a project listed
here that isn't, send a patch for this HTML file to the <a
href="mailto:java-patches@gcc.gnu.org";>java-patches</a> list.
+</p>
-<p>
-
-<br>
+<br />
<table border="0" cellpadding="4" width="95%">
<tr bgcolor="#b0d0ff">
<th align="left">
@@ -29,12 +28,14 @@ jar support
</th>
</tr>
</table>
-<br>
+<br />
+
+<p>
Modify gcj to obey the constraints layed out by the jar file
manifest file.
-<p>
+</p>
-<br>
+<br />
<table border="0" cellpadding="4" width="95%">
<tr bgcolor="#b0d0ff">
<th align="left">
@@ -42,17 +43,18 @@ Plugin for Mozilla
</th>
</tr>
</table>
-<br>
+<br />
+<p>
<a href="http://mozilla.org/";>Mozilla</a> is open-source web browser,
designed for standards compliance, performance and portability. The
<a href="http://www.mozilla.org/oji/";>Open JVM Integration project</a>
(OJI) is a Mozilla sub-project, and is working to extend the browser
to allow Java virtual machines to be plugged into Mozilla. A gij
based plugin would be very nice indeed (gijzilla?).
-<p>
+</p>
-<br>
+<br />
<table border="0" cellpadding="4" width="95%">
<tr bgcolor="#b0d0ff">
<th align="left">
@@ -60,12 +62,14 @@ Benchmark infrastructure
</th>
</tr>
</table>
-<br>
+<br />
+<p>
Measuring performance is tricky business. We currently do all our
performance measurements in an ad hoc manner. What is needed is some
infrastructure we can use to track performance regressions and
identify opportunities for improvement.
+</p>
<p>
<a href="mailto:bryce@albatross.co.nz";>Bryce McKinlay</a> has put
together a list of some <a
@@ -74,8 +78,9 @@ GCJ</a>. IBM has also recently released
called <a
href="http://oss.software.ibm.com/developerworks/opensource/jmocha/index.html";>jMocha</a>. Building
some infrastructure around these would be incredibly useful.
-<p>
+</p>
+<br />
<table border="0" cellpadding="4" width="95%">
<tr bgcolor="#b0d0ff">
<th align="left">
@@ -83,12 +88,12 @@ Performance improvements
</th>
</tr>
</table>
-<br>
+<br />
There are a few concrete performance improvements that we already know
we want:
<ul>
- <li>If an object or array is allocated in static code that is
+ <li><p>If an object or array is allocated in static code that is
executed at most once (i.e. not in a loop or in a non-private
method), then we have the option of pre-allocating the object
or array in the static data or bss segment. This is most
@@ -99,7 +104,7 @@ we want:
are initialized to link-time constants, such as references
to other statically allocated objects, as you might get
from a multi-dimensional array brace-initializer.
- <p>
+ </p><p>
It may also make sense to pre-allocate a non-array object.
It makes most sense when the object constructor is inlined,
especially if it turns out that most or all of the fields get
@@ -108,7 +113,7 @@ we want:
being assigned to a static final field: The tradeoff is that
you save the space needed for the call to allocate the object, but
you use more space if it turns out the class is never initialized.
- <p>
+ </p><p>
Note that if a statically allocated object contains
pointer fields then the gc has to know about the object.
The cleanest way is to make sure the object header has
@@ -117,9 +122,10 @@ we want:
static object with the gc, since if it is live, it will get
traversed anyway (typically via the fields table of the declaring
class).
+ </p></li>
</ul>
-<p>
+<br />
<table border="0" cellpadding="4" width="95%">
<tr bgcolor="#b0d0ff">
<th align="left">
@@ -127,19 +133,19 @@ Compiler improvements
</th>
</tr>
</table>
-<br>
+<br />
<ul>
<li>We'd like gcj to do tree-level inlining like the C++
compiler. We're most of the way there (when compiling
from Java source code), since gcj already represents
- entire functions as trees.
+ entire functions as trees.</li>
<li>Once we have tree-level inlining, we can use it to
sometimes eliminate unnecessary synchronizations.
Combined with a simple "no escape" flag, this could also
let us further optimize string concatenation without
- having to introduce a new class in the runtime.
+ having to introduce a new class in the runtime.</li>
<li>When compiling from bytecode, GCJ generates tree nodes
as long as it is within a single "statement" - i.e. no branching
@@ -161,19 +167,19 @@ Compiler improvements
The simplification is probably best done after we have generated
a correct but <code>GOTO</code>-based tree representation.
For example, if a label is only used once, we can move its code
- to where the unique <code>GOTO</code> is.
+ to where the unique <code>GOTO</code> is.</li>
<li>Add hooks to gcj and g++ to generate write barriers.
- This would let us write a precise collector.
+ This would let us write a precise collector.</li>
<li>Do escape analysis to detect method-local and
thread-local objects. This can yield a significant
- performance improvement in some cases.
+ performance improvement in some cases.</li>
<li>Extend the existing null-pointer patch (for PR 2) to
optionally enable it for all method calls and field
dereferences. This will let gcj-compiled code work
- correctly on systems without an MMU.
+ correctly on systems without an MMU.</li>
<li>The structure of <code>expand_byte_code</code> in
<code>expr.c</code> uses macros in a way that in retrospect
@@ -183,10 +189,10 @@ Compiler improvements
(There are actually two switch statements using the magic macros
in <code>expr.c</code> - look for the includes of
<code>"javaop.def"</code>. They should both be re-written, but
- second one is higher priority.)
+ second one is higher priority.)</li>
</ul>
-<p>
+<br />
<table border="0" cellpadding="4" width="95%">
<tr bgcolor="#b0d0ff">
<th align="left">
@@ -194,15 +200,13 @@ Runtime improvements
</th>
</tr>
</table>
-<br>
+<br />
<ul>
<li>Write a program to convert existing locale data into a
- format we can use.
-
+ format we can use.</li>
</ul>
-<p>
-</GCJNAV>
+</gcjnav>
</body>
</html>
Index: java/test.html
===================================================================
RCS file: /cvsroot/gcc/wwwdocs/htdocs/java/test.html,v
retrieving revision 1.7
diff -u -3 -p -r1.7 test.html
--- java/test.html 12 Nov 2001 06:06:30 -0000 1.7
+++ java/test.html 23 Mar 2002 22:05:15 -0000
@@ -1,8 +1,10 @@
<html>
+<head>
<title>GCJ - Testing</title>
-<body bgcolor="white">
+</head>
+<body>
-<GCJNAV>
+<gcjnav>
<h1>Testing GCJ</h1>
@@ -13,37 +15,37 @@
</th>
</tr>
</table>
-<br>
+<br />
-Runtime tests are executed via <tt>'make check'</tt> from the <tt>testsuite</tt>
-directory of the libjava hierarchy in the build tree. Additional
+<p>Runtime tests are executed via <tt>'make check'</tt> from the <tt>testsuite
+</tt> directory of the libjava hierarchy in the build tree. Additional
<a href="contrib.html#Testing">runtime tests</a> can be checked into the tree.
Regression tests of the core packages in libgcj are run automatically via the
<a href="#Mauve">Mauve test suite (described below)</a> if it is made available
-when the tests are being run.<p>
+when the tests are being run.</p>
<table border="0" cellpadding="4" width="95%">
<tr bgcolor="#b0d0ff">
<th align="left">
- <a name=Mauve>Mauve</a>
+ <a name="Mauve">Mauve</a>
</th>
</tr>
</table>
-<br>
+<br />
-The <a href="http://sources.redhat.com/mauve/";>Mauve Project</a> is a
+<p>The <a href="http://sources.redhat.com/mauve/";>Mauve Project</a> is a
project to write a suite of tests for the Java Class Libraries. We
-encourage developers to contribute test cases to Mauve.<p>
+encourage developers to contribute test cases to Mauve.</p>
-libgcj supports Mauve testing. If you have Mauve checked out in,
+<p>libgcj supports Mauve testing. If you have Mauve checked out in,
e.g., <tt>~/mauve/</tt>, then you can tell the libgcj to run the Mauve
-tests like so: <tt>make MAUVEDIR=~/mauve check</tt>.<p>
+tests like so: <tt>make MAUVEDIR=~/mauve check</tt>.</p>
-To highlight regressions, a mechanism has been set up in <tt>mauve.exp</tt>
+<p>To highlight regressions, a mechanism has been set up in <tt>mauve.exp</tt>
to track expected failures by comparing against the contents of
<tt>libjava/testsuite/libjava.mauve/xfails</tt> from the source hierarchy.
This file should be updated as new (failing) tests are added to Mauve or when
-fixes are made to libgcj that correct for failing Mauve tests.<p>
+fixes are made to libgcj that correct for failing Mauve tests.</p>
<table border="0" cellpadding="4" width="95%">
<tr bgcolor="#b0d0ff">
@@ -52,18 +54,18 @@ fixes are made to libgcj that correct fo
</th>
</tr>
</table>
-<br>
+<br />
-The <a
+<p>The <a
href="http://oss.software.ibm.com/developerworks/opensource/jacks/";>Jacks</a>
project exists to create a test suite for Java compilers. We
-encourage developers to contribute test cases to Jacks.<p>
+encourage developers to contribute test cases to Jacks.</p>
-Changes affecting the gcj front end can usefully be tested against
+<p>Changes affecting the gcj front end can usefully be tested against
Jacks. We don't as yet have an automated mechanism to run Jacks tests
-in our test framework.<p>
+in our test framework.</p>
-</GCJNAV>
+</gcjnav>
</body>
</html>
Index: java/thanks.html
===================================================================
RCS file: /cvsroot/gcc/wwwdocs/htdocs/java/thanks.html,v
retrieving revision 1.27
diff -u -3 -p -r1.27 thanks.html
--- java/thanks.html 15 Mar 2002 22:56:12 -0000 1.27
+++ java/thanks.html 23 Mar 2002 22:05:16 -0000
@@ -6,9 +6,9 @@
<body>
-<GCJNAV>
+<gcjnav>
-<br><br>
+<br /><br />
<h1>GCJ Credits</h1>
<table border="0" cellpadding="4" width="95%">
@@ -18,7 +18,7 @@
</th>
</tr>
</table>
-<br>
+<br />
Many people contribute to the GCJ project, and in many different
capacities. Any omissions to this list are accidental. Feel free to
@@ -26,120 +26,119 @@ contact <a href="mailto:green@cygnus.com
have been left out or some of your contributions are not listed.
<!-- Please keep this list in alphabetical order. -->
-<p>
<ul>
-<li>Godmar Back for his improvements and encouragement.
-<li>Scott Bambrough for help porting the compiler.
-<li>Jon Beniston for his Win32 port.
-<li>Geoff Berry for his object serialization work and various patches.
+<li>Godmar Back for his improvements and encouragement.</li>
+<li>Scott Bambrough for help porting the compiler.</li>
+<li>Jon Beniston for his Win32 port.</li>
+<li>Geoff Berry for his object serialization work and various patches.</li>
<li>Eric Blake for helping to make gcj and libgcj conform to the
-specifications.
+specifications.</li>
<li>Hans-J. Boehm for his <a
href="http://www.hpl.hp.com/personal/Hans_Boehm/gc/";>garbage
-collector</a>, IA-64 libffi port, and other work.
-<li>Per Bothner for dreaming up, designing and implementing much of gcj.
-<li>Joerg Brunsmann for compiler hacking and help with the FAQ.
-<li>Steve Chamberlain for config fixes and the picoJava port.
-<li>Glenn Chambers for help with the FAQ.
-<li>John-Marc Chandonia for various library patches.
-<li>Eric Christopher for his porting help and clean-ups.
+collector</a>, IA-64 libffi port, and other work.</li>
+<li>Per Bothner for dreaming up, designing and implementing much of gcj.</li>
+<li>Joerg Brunsmann for compiler hacking and help with the FAQ.</li>
+<li>Steve Chamberlain for config fixes and the picoJava port.</li>
+<li>Glenn Chambers for help with the FAQ.</li>
+<li>John-Marc Chandonia for various library patches.</li>
+<li>Eric Christopher for his porting help and clean-ups.</li>
<li>The <a href="http://www.classpath.org";>GNU Classpath project</a>
-for all of their merged runtime code.
-<li>Mo DeJong for gcj and libgcj bug fixes.
+for all of their merged runtime code.</li>
+<li>Mo DeJong for gcj and libgcj bug fixes.</li>
<li>The GCC project <a
href="http://gcc.gnu.org/onlinedocs/gcc/Contributors.html";>contributors</a>
-for all of their great compiler work.
-<li>Ivan Fontes Garcia for the Portugese translation of the FAQ.
-<li>John Gilmore for a donation to the FSF earmarked improving GNU Java.
-<li>Anthony Green for various contributions.
-<li>Stu Grossman for gdb hacking, allowing us to debug our code.
-<li>Andrew Haley for his amazing compiler and library efforts.
-<li>Jakub Jelinek for improving the build system.
-<li>Warren Levy for his tremendous library work.
-<li>Oskar Liljeblad for hacking on AWT and his many bug reports and patches.
+for all of their great compiler work.</li>
+<li>Ivan Fontes Garcia for the Portugese translation of the FAQ.</li>
+<li>John Gilmore for a donation to the FSF earmarked improving GNU Java.</li>
+<li>Anthony Green for various contributions.</li>
+<li>Stu Grossman for gdb hacking, allowing us to debug our code.</li>
+<li>Andrew Haley for his amazing compiler and library efforts.</li>
+<li>Jakub Jelinek for improving the build system.</li>
+<li>Warren Levy for his tremendous library work.</li>
+<li>Oskar Liljeblad for hacking on AWT and his many bug reports and patches.</li>
<li>All of the Mauve project <a
-href="http://sources.redhat.com/cgi-bin/cvsweb.cgi/~checkout~/mauve/THANKS?rev=1.2&cvsroot=mauve&only_with_tag=HEAD";>contributors</a>,
-for test code.
-<li>Bryce McKinlay for numerous gcj and libgcj fixes and improvements.
-<li>Adam Megacz for his work on the Win32 port.
+href="http://sources.redhat.com/cgi-bin/cvsweb.cgi/~checkout~/mauve/THANKS?rev=1.2&cvsroot=mauve&only_with_tag=HEAD";>contributors</a>,
+for test code.</li>
+<li>Bryce McKinlay for numerous gcj and libgcj fixes and improvements.</li>
+<li>Adam Megacz for his work on the Win32 port.</li>
<li>Jason Molenda for establishing the project infrastructure on
-<a href="http://sources.redhat.com";>sources.redhat.com</a>.
-<li>Mike Moreton for his various patches.
-<li>Alexandre Oliva for all of this porting and testing efforts.
-<li>Rainer Orth for configuration clean-ups and porting help.
+<a href="http://sources.redhat.com";>sources.redhat.com</a>.</li>
+<li>Mike Moreton for his various patches.</li>
+<li>Alexandre Oliva for all of this porting and testing efforts.</li>
+<li>Rainer Orth for configuration clean-ups and porting help.</li>
<li>Alexandre Petit-Bianco for implementing much of the compiler, and
-continued maintainership.
-<li>Rolf W. Rasmussen for hacking on AWT.
-<li>Bradley Schatz for his work on the FAQ.
-<li>Jason Schroeder for jcf-dump patches.
-<li>John Stracke for his HTTP protocol fixes.
-<li>Jeff Sturm for porting help, bug fixes, and encouragement.
-<li>Kresten Krab Thorup for his fantastic bytecode interpreter.
-<li>Andreas Tobler for his work porting libgcj to Darwin.
-<li>Tom Tromey for his many contributions and libgcj maintainership.
-<li>Matt Welsh for help with Linux Threads.
-<li>Urban Widmark for help fixing java.io.
-<li>Mark Wielaard for new library code and his work integrating with Classpath.
-<li>Gilles Zunino for help porting to Irix.
+continued maintainership.</li>
+<li>Rolf W. Rasmussen for hacking on AWT.</li>
+<li>Bradley Schatz for his work on the FAQ.</li>
+<li>Jason Schroeder for jcf-dump patches.</li>
+<li>John Stracke for his HTTP protocol fixes.</li>
+<li>Jeff Sturm for porting help, bug fixes, and encouragement.</li>
+<li>Kresten Krab Thorup for his fantastic bytecode interpreter.</li>
+<li>Andreas Tobler for his work porting libgcj to Darwin.</li>
+<li>Tom Tromey for his many contributions and libgcj maintainership.</li>
+<li>Matt Welsh for help with Linux Threads.</li>
+<li>Urban Widmark for help fixing java.io.</li>
+<li>Mark Wielaard for new library code and his work integrating with Classpath.</li>
+<li>Gilles Zunino for help porting to Irix.</li>
</ul>
We'd also like to thank the folks who have contributed time and energy
in testing GCJ:
<ul>
-<li>Michael Abd-El-Malek
-<li>Thomas Arend
-<li>Bonzo Armstrong
-<li>Steven Ashe
-<li>Chris Baldwin
-<li>David Billinghurst
-<li>Jim Blandy
-<li>Stephane Bortzmeyer
-<li>Frank Braun
-<li>Sidney Cadot
-<li>Bradford Castalia
-<li>Ralph Doncaster
-<li>Richard Emberson
-<li>Graham Fawcett
-<li>Robert A. French
-<li>Mark K. Gardner
-<li>Charles-Antoine Gauthier
-<li>Simon Gornall
-<li>Fred Gray
-<li>John Griffin
-<li>Patrik Hagglund
-<li>Phil Hargett
-<li>Amancio Hasty
-<li>Bryan W. Headley
-<li>Kevin B. Hendricks
-<li>Joep Jansen
-<li>David Kidd
-<li>Tobias Kuipers
-<li>Anand Krishnaswamy
-<li>H.J. Lu
-<li>Jesse Macnish
-<li>Anon A. Mous
-<li>Stefan Morrell
-<li>Pekka Nikander
-<li>Jon Olson
-<li>Magnus Persson
-<li>Chris Pollard
-<li>Paul Reilly
-<li>Tom Reilly
-<li>Torsten Rueger
-<li>Danny Sadinoff
-<li>Marc Schifer
-<li>Franz Sirl
-<li>Tim Souder
-<li>Adam Sulmicki
-<li>Frederik Warg
-<li>Gregory Warnes
-<li>David E. Young
+<li>Michael Abd-El-Malek</li>
+<li>Thomas Arend</li>
+<li>Bonzo Armstrong</li>
+<li>Steven Ashe</li>
+<li>Chris Baldwin</li>
+<li>David Billinghurst</li>
+<li>Jim Blandy</li>
+<li>Stephane Bortzmeyer</li>
+<li>Frank Braun</li>
+<li>Sidney Cadot</li>
+<li>Bradford Castalia</li>
+<li>Ralph Doncaster</li>
+<li>Richard Emberson</li>
+<li>Graham Fawcett</li>
+<li>Robert A. French</li>
+<li>Mark K. Gardner</li>
+<li>Charles-Antoine Gauthier</li>
+<li>Simon Gornall</li>
+<li>Fred Gray</li>
+<li>John Griffin</li>
+<li>Patrik Hagglund</li>
+<li>Phil Hargett</li>
+<li>Amancio Hasty </li>
+<li>Bryan W. Headley</li>
+<li>Kevin B. Hendricks</li>
+<li>Joep Jansen</li>
+<li>David Kidd</li>
+<li>Tobias Kuipers</li>
+<li>Anand Krishnaswamy</li>
+<li>H.J. Lu</li>
+<li>Jesse Macnish</li>
+<li>Anon A. Mous</li>
+<li>Stefan Morrell</li>
+<li>Pekka Nikander</li>
+<li>Jon Olson</li>
+<li>Magnus Persson</li>
+<li>Chris Pollard</li>
+<li>Paul Reilly</li>
+<li>Tom Reilly</li>
+<li>Torsten Rueger</li>
+<li>Danny Sadinoff</li>
+<li>Marc Schifer</li>
+<li>Franz Sirl</li>
+<li>Tim Souder</li>
+<li>Adam Sulmicki</li>
+<li>Frederik Warg</li>
+<li>Gregory Warnes</li>
+<li>David E. Young</li>
</ul>
Thank you all!
-</GCJNAV>
+</gcjnav>
</body>
</html>
Index: java/tm.html
===================================================================
RCS file: /cvsroot/gcc/wwwdocs/htdocs/java/tm.html,v
retrieving revision 1.12
diff -u -3 -p -r1.12 tm.html
--- java/tm.html 8 Feb 2001 17:34:35 -0000 1.12
+++ java/tm.html 23 Mar 2002 22:05:16 -0000
@@ -1,15 +1,17 @@
<html>
+<head>
<title>GCJ - About</title>
-<body bgcolor="white">
+</head>
+<body>
-<GCJNAV>
+<gcjnav>
Java and all Java-based marks are trademarks or registered trademarks
of Sun Microsystems, Inc. in the United States and other countries.
The Free Software Foundation, Cygnus Solutions and Red Hat are
independent of Sun Microsystems, Inc.
-</GCJNAV>
+</gcjnav>
</body>
</html>