<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
On 30/04/11 00:05, Kelly O'Hair wrote:
<blockquote
cite="mid:C1EB8205-AE42-4988-90E1-2AB89BC81797@oracle.com"
type="cite"><br>
<div>
<div>On Apr 29, 2011, at 1:31 PM, Steve Poole wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div text="#000000" bgcolor="#ffffff"> On 26/04/11 15:54,
Kelly O'Hair wrote:
<blockquote
cite="mid:52703127-B2C9-479E-A48B-810F200C49EA@oracle.com"
type="cite"><br>
<div>
<div>On Apr 26, 2011, at 12:59 AM, Steve Poole wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite"><span class="Apple-style-span"
style="border-collapse: separate; font-family:
Times; font-style: normal; font-variant: normal;
font-weight: normal; letter-spacing: normal;
line-height: normal; orphans: 2; text-indent: 0px;
text-transform: none; white-space: normal; widows:
2; word-spacing: 0px; font-size: medium;">
<blockquote
cite="mid:4FD1ED99-3447-4339-9C41-0897043BF8B6@oracle.com"
type="cite">
<div>
<blockquote type="cite">
<div style="word-wrap: break-word;">
<div>
<pre style="white-space: pre-wrap;"><span class="Apple-style-span" style="font-family: Courier; font-size: 14px;">
* Allow for use of more portable build tools (compilers etc.) where possible</span></pre>
</div>
</div>
</blockquote>
</div>
</blockquote>
Can I add support for alternative JVM's ?</span></blockquote>
<br>
</div>
<div>Seems a bit out of scope to me.</div>
<div><br>
</div>
</blockquote>
Sorry, it was a bit of a flippant one liner, I owe you
more details. <br>
<br>
There are three usecases I see that require the OpenJDK
build process to be modified to accommodate:<br>
<br>
The first is bootstrapping a build. I'd like to be able to
build OpenJDK on a new platform without the need for a
previous SDK build to be present. <br>
In this usecase it's possible that an simple interpreter
based JVM would be sufficient (ie Zero) (or even maybe a
cross compiling mode)</div>
</blockquote>
</div>
<div>
<blockquote type="cite">
<div text="#000000" bgcolor="#ffffff"> <br>
The second is getting OpenJDK to build on a platform where
a hotspot JVM doesn't exist and may never exist. As you
guess I'm thinking of IBM platforms specifically. I'm don't
expect to port Hotspot to AIX so I need to be able to make
the OpenJDK build work with J9. <br>
<font class="Apple-style-span" color="#000000"><font
class="Apple-style-span" color="#144fae"><br>
</font></font></div>
</blockquote>
<blockquote type="cite">
<div text="#000000" bgcolor="#ffffff"> The third (a variant of
the 2nd) is where another JVM vendor wants to get OpenJDK
working with their JVM - regardless of the availability of a
Hotspot JVM on the target platform.<br>
<br>
To be clear. I'm not suggesting that this project step up
to defining the interfaces between JVM and classes. This
is simple pragmatics. The Hotspot JVM is the starting point
for the mould and I would expect to make J9 (or any new JVM)
fit into it as much as possible. However there will be
changes needed. These are mostly simple, like
parameterising JVM command line options, to the more
complicated like separating out JVM intrinsic classes such
as String.java, Object.java, Thread.java etc so that the
right versions get build and packaged.<br>
</div>
</blockquote>
</div>
<br>
<div>I certainly can understand these needs, but it is still seems
beyond the initial scope of this project.</div>
<div>Maybe in a phase 2?</div>
</blockquote>
<br>
Hmm, maybe doing all of them in one go may be a stretch :-) The 2nd
usecase is fundamental though to supporting IBM platforms, something
you mentioned you wanted to do. Is there any reason why realising
that usecase is beyond phase 1?<br>
<br>
<br>
<blockquote
cite="mid:C1EB8205-AE42-4988-90E1-2AB89BC81797@oracle.com"
type="cite">
<div><br>
</div>
<div>-kto</div>
<div><br>
</div>
</blockquote>
<br>
</body>
</html>