public inbox for java-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: Steven Bosscher <stevenb.gcc@gmail.com>
Cc: gcc-patches@gcc.gnu.org, java-patches@gcc.gnu.org
Subject: Re: [wwwdocs] Use regular <h2> markup for java/projects.html
Date: Sun, 08 May 2011 23:01:00 -0000	[thread overview]
Message-ID: <alpine.LNX.2.00.1105090053410.3911@gerinyyl.fvgr> (raw)
In-Reply-To: <BANLkTinCY6PXb_2Zf4Gmppvi3XnPOc27FQ@mail.gmail.com>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 3224 bytes --]

On Sat, 30 Apr 2011, Steven Bosscher wrote:
>> 2011-04-26  Gerald Pfeifer  <gerald@pfeifer.com>
>>
>>        * projects.html: Use regular <h2> markup for section headers
>>        instead of fake tables.
> The "Compiler improvements" section is 10 years behind on GCC's
> development (tree-ssa!). The "recently released" jMocha is from 2000
> and I can't find it anywhere for download. The "Open JVM Integration"
> is obsolete. There is very little on this page that is still useful
> information for someone willing to contribute to GCJ...

Hard to disagree, Steven.  It's just that I am not to well aware of
what's happening in Java land.

I was hoping my patch made it easier for someone with more background
to update this page in terms of contents, but seeing that nobody took
action on your analysis I cooked up the patch below which I plan on 
committing in a couple of days.

Gerald

2011-05-09  Gerald Pfeifer  <gerald@pfeifer.com>

	* projects.html: Update name of java mailing list.
	(Plugin for Mozilla): Remove section.
	(Compiler Improvements): Remove tree inlining item.
	(Benchmark infrastructure): Remove reference to jMocha.

Index: projects.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/java/projects.html,v
retrieving revision 1.34
diff -u -r1.34 projects.html
--- projects.html	26 Apr 2011 20:25:34 -0000	1.34
+++ projects.html	8 May 2011 22:59:49 -0000
@@ -12,7 +12,7 @@
 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
 to the <a
-href="mailto:java@gcc.gnu.org">java-discuss</a>
+href="mailto:java@gcc.gnu.org">java</a>
 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.
@@ -27,18 +27,6 @@
 </p>
 
 
-<h2>Plugin for Mozilla</h2>
-
-<p>
-<a href="http://www.mozilla.org/">Mozilla</a> is open-source web browser,
-designed for standards compliance, performance and portability.  The
-Open JVM Integration project (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>
-
-
 <h2>Benchmark infrastructure</h2>
 
 <p>
@@ -49,8 +37,7 @@
 </p>
 <p>
 <a href="mailto:bryce@albatross.co.nz">Bryce McKinlay</a> has put
-together a list of some benchmarks that run on GCJ.  IBM has also
-recently released a set of "micro benchmarks" called jMocha.
+together a list of some benchmarks that run on GCJ.
 Building some infrastructure around these would be incredibly useful.
 </p>
 
@@ -97,11 +84,6 @@
 <h2>Compiler improvements</h2>
 
 	  <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.</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

  reply	other threads:[~2011-05-08 23:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-30 12:11 Gerald Pfeifer
2011-04-30 14:05 ` Steven Bosscher
2011-05-08 23:01   ` Gerald Pfeifer [this message]
2011-05-13 10:28     ` Gerald Pfeifer

Reply instructions:

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

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

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

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

  git send-email \
    --in-reply-to=alpine.LNX.2.00.1105090053410.3911@gerinyyl.fvgr \
    --to=gerald@pfeifer.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=java-patches@gcc.gnu.org \
    --cc=stevenb.gcc@gmail.com \
    /path/to/YOUR_REPLY

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

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