[ Date Prev][ Date Next][ Thread Prev][ Thread Next][ Date Index][ Thread Index]
C++ ABI Summary
- To: cxx-abi@xxxxxxxxxxxx
- Subject: C++ ABI Summary
- From: Jim Dehnert <dehnert@xxxxxxx>
- Date: Wed, 09 Jun 1999 14:00:15 -0700
Attached is an updated issue summary, with phone information for tomorrow.
The meeting is in the same place, and will run from 10-12 instead of 11-1.
The agenda is to begin discussion of object layout issues, starting with
a presentation by Matt Austern. Please send any documentation to the group
as early as possible...
--
- Jim Dehnert dehnert@xxxxxxx
(650)933-4272 <HTML>
<HEAD>
<title>C++ ABI Summary</title>
<style type="text/css">
<!--
TT {font-size: 10pt; font-weight: bold}
TD {font-size: 10pt}
-->
</style>
<hr>
<font size=6><i><b>
<p>
C++ ABI Summary
</b></i></font>
<!-- font size=-1 -->
<p>
<i>Revised 8 June 1999</i>
</center>
</HEAD>
<BODY>
<p>
<hr>
<p>
<h4>Meetings</h4>
<p>
<table border=on cellpadding=3>
<tr>
<th colspan=2> When </th>
<th> Where </th>
<th> Phone </th>
<th> Reservation </th>
<th> Passcode </th>
</tr>
<tr>
<td> 3 June </td> <td> 11:00-13:00 </td>
<td align=left colspan=4> completed </td>
</tr>
<tr>
<td> 10 June </td>
<td> 10:00-12:00 </td>
<td> SGI Sapphire 20L </td>
<td> 916-356-9200 </td>
<td> 6-136000 </td>
<td> 822-6418 </td>
</tr>
<tr>
<td> 17 June </td>
<td> 10:00-12:00 </td>
<td> SGI Garnet 20L </td>
<td> 650-933-7976 </td> <td> </td> <td> </td>
</tr>
<tr>
<td> 24 June </td>
<td> 10:00-12:00 </td>
<td> SGI Sapphire 20L </td>
<td> 650-933-7976 </td> <td> </td> <td> </td>
</tr>
<tr>
<td> 1 July </td>
<td> 10:00-12:00 </td>
<td> SGI Sapphire 20L </td>
<td> 650-933-7976 </td> <td> </td> <td> </td>
</tr>
<tr>
<td> 8 July </td>
<td> 10:00-12:00 </td>
<td> SGI Sapphire 20L </td>
<td> 650-933-7976 </td> <td> </td> <td> </td>
</tr>
<tr>
<td> 15 July </td>
<td> 10:00-12:00 </td>
<td> SGI Sapphire 20L </td>
<td> 650-933-7976 </td> <td> </td> <td> </td>
</tr>
<tr>
<td> 22 July </td>
<td> 10:00-12:00 </td>
<td> SGI Sapphire 20L </td>
<td> 650-933-7976 </td> <td> </td> <td> </td>
</tr>
<tr>
<td> 29 July </td>
<td> 10:00-12:00 </td>
<td> SGI Sapphire 20L </td>
<td> 650-933-7976 </td> <td> </td> <td> </td>
</tr>
<tr>
<td> 5 August </td>
<td> 10:00-12:00 </td>
<td> SGI Sapphire 20L </td>
<td> 650-933-7976 </td> <td> </td> <td> </td>
</tr>
<tr>
<td> 12 August </td>
<td> 10:00-12:00 </td>
<td> SGI Sapphire 20L </td>
<td> 650-933-7976 </td> <td> </td> <td> </td>
</tr>
<tr>
<td> 19 August </td>
<td> 10:00-12:00 </td>
<td> SGI Sapphire 20L </td>
<td> 650-933-7976 </td> <td> </td> <td> </td>
</tr>
</table>
<p>
Note: When calling the SGI telephone bridges (starting 17 June),
the first caller continues to ring until the second party joins.
To get rid of it, you can call from a second phone,
and I believe you can hang it up right away.
<p>
<hr>
<p>
<h4>Participants</h4>
<p>
<table border=on cellpadding=3>
<tr>
<th> Company </th>
<th> Name </th>
<th> Telephone </th>
<th> Fax </th>
<th> Email </th>
</tr>
<tr>
<th rowspan=1> </th>
<td colspan=3> overall reflector </td>
<td> <a href=mailto:cxx-abi@xxxxxxxxxxxxxxxxxxxx>cxx-abi@xxxxxxxxxxxx</a> </td>
</tr>
<tr>
<th rowspan=6> SGI </th>
<td> Jim Dehnert </td>
<td> (650) 933-4272 </td>
<td> (650) 932-4272 </td>
<td> <a href=mailto:dehnert@xxxxxxx> dehnert@xxxxxxx </a></td>
</tr>
<tr>
<td> Matt Austern </td>
<td> (650) 933-4196 </td>
<td> (650) 932-4196 </td>
<td> <a href=mailto:austern@xxxxxxxxxxxx> austern@xxxxxxxxxxxx </a></td>
</tr>
<tr>
<td> Hans Boehm </td>
<td> (650) 933-7144 </td>
<td> (650) 932-7144 </td>
<td> <a href=mailto:boehm@xxxxxxxxxxxx> boehm@xxxxxxxxxxxx </a></td>
</tr>
<tr>
<td> Shin-Ming Liu </td>
<td> (650) 933-4287 </td>
<td> (650) 932-4287 </td>
<td> <a href=mailto:shin@xxxxxxxxxxxx> shin@xxxxxxxxxxxx </a></td>
</tr>
<tr>
<td> John Wilkinson </td>
<td> (650) 933-4298 </td>
<td> (650) 932-4298 </td>
<td> <a href=mailto:jfw@xxxxxxxxxxxx> jfw@xxxxxxxxxxxx </a></td>
</tr>
<tr>
<td colspan=3> reflector </td>
<td> <a href=mailto:cxx-abi-sgi@xxxxxxxxxxxx>
cxx-abi-sgi@xxxxxxxxxxxx </a></td>
</tr>
<tr>
<th rowspan=4> Cygnus </th>
<td> Jason Merrill </td>
<td> (408) 542-9665 </td>
<td> (408) 542-9765 </td>
<td> <a href=mailto:jason@xxxxxxxxxx> jason@xxxxxxxxxx </a></td>
</tr>
<tr>
<td> Ian Carmichael </td>
<td> (416) 482-3946 </td>
<td> (416) 482-6299 </td>
<td> <a href=mailto:iancarm@xxxxxxxxxx> iancarm@xxxxxxxxxx </a></td>
</tr>
<tr>
<td> Ulrich Drepper </td>
<td> (408) 765-4699 </td>
<td> ? </td>
<td> <a href=mailto:drepper@xxxxxxxxxx> drepper@xxxxxxxxxx </a></td>
</tr>
<tr>
<td colspan=3> reflector </td>
<td> <a href=mailto:c++abi@xxxxxxxxxx> c++abi@xxxxxxxxxx </a></td>
</tr>
<tr>
<th rowspan=4> Hewlett- Packard </th>
<td> Cary Coutant </td>
<td> (408) 447-5759 </td>
<td> ? </td>
<td> <a href=mailto:cary@xxxxxxxxxx> cary@xxxxxxxxxx </a></td>
</tr>
<tr>
<td> Christophe de Dinechin </td>
<td> (408) 447-5491 </td>
<td> ? </td>
<td> <a href=mailto:ddd@xxxxxxxxxx> ddd@xxxxxxxxxx </a></td>
</tr>
<tr>
<td> Sassan Hazeghi </td>
<td> (408) 447-5007 </td>
<td> ? </td>
<td> <a href=mailto:sassan@xxxxxxxxxx> sassan@xxxxxxxxxx </a></td>
</tr>
<tr>
<td colspan=3> reflector </td>
<td> <a href=mailto:cxx-abi-hp@xxxxxxxxxxxxxxxxxx>
cxx-abi-hp@xxxxxxxxxxxxxxxxxx </a></td>
</tr>
<tr>
<th rowspan=3> IBM </th>
<td> Mark Mendell </td>
<td> (416) 448-3485 </td>
<td> (416) 448-4414 </td>
<td> <a href=mailto:mendell@xxxxxxxxxx> mendell@xxxxxxxxxx </a></td>
</tr>
<tr>
<td> Allan H. Kielstra </td>
<td> (416) 448-3558 </td>
<td> (416) 448-4414 </td>
<td> <a href=mailto:kielstra@xxxxxxxxxx> kielstra@xxxxxxxxxx </a></td>
</tr>
<tr>
<td colspan=3> reflector </td>
<td> <a href=mailto:CxxABI-ADTC-CAN@xxxxxxxxxx>
CxxABI-ADTC-CAN@xxxxxxxxxx </a></td>
</tr>
<tr>
<th rowspan=3> Intel </th>
<td> Sunil Saxena </td>
<td> (408) 765-5272 </td>
<td> (408) 653-8511 </td>
<td> <a href=mailto:Sunil.Saxena@xxxxxxxxx> Sunil.Saxena@xxxxxxxxx </a></td>
</tr>
<tr>
<td> Priti Shrivastav </td>
<td> (408) 765-4699 </td>
<td> ? </td>
<td> <a href=mailto:Priti.Shrivastav@xxxxxxxxx>
Priti.Shrivastav@xxxxxxxxx </a></td>
</tr>
<tr>
<td colspan=3> reflector </td>
<td> <a href=mailto:cxx-abi@xxxxxxxxxxxxxxxxxxxx>
cxx-abi@xxxxxxxxxxxxxxxxxxxx </a></td>
</tr>
<tr>
<th rowspan=1> SCO </th>
<td> Jonathan Schilling </td>
<td> (908) 790-2364 </td>
<td> (908) 790-2426 </td>
<td> <a href=mailto:jls@xxxxxxx> jls@xxxxxxx </a></td>
</tr>
<tr>
<th rowspan=4> Sun </th>
<td> George Vasick </td>
<td> (650) 786-5123 </td>
<td> (650) 786-9551 </td>
<td> <a href=mailto:george.vasick@xxxxxxxxxxx>
george.vasick@xxxxxxxxxxx <a></td>
</tr>
<tr>
<td> Michael Lam </td>
<td> (650) 786-3492 </td>
<td> (650) 786-9551 </td>
<td> <a href=mailto:michael.lam@xxxxxxxxxxx> michael.lam@xxxxxxxxxxx </a></td>
</tr>
<tr>
<td> Michael Ball </td>
<td> (650) 786-9109 </td>
<td> (650) 786-9551 </td>
<td> <a href=mailto:michael.ball@xxxxxxxxxxx> michael.ball@xxxxxxxxxxx </a></td>
</tr>
<tr>
<td> Reza Monajjemi </td>
<td> (650) 786-6175 </td>
<td> ? </td>
<td> <a href=mailto:reza.monajjemi@xxxxxxxxxxx>
reza.monajjemi@xxxxxxxxxxx </a></td>
</tr>
</table>
<p>
<hr>
<p>
<h4> Objectives </h4>
<ul>
<p>
<li>
Interoperable C++ compilation on IA-64:
we want users to be able to build relocatable objects with
different compilers and link them together,
and if possible even to ship common DSOs.
This objective implies agreement on:
<ul>
<li> Data representation
<li> Object file representation
<li> Library API
</ul>
<p>
<li>
ISO Standard C++:
highest priority is functionality and performance of standard-compliant code.
It should not be sacrificed for the benefit of language extensions or
legacy implementations (though considering them as tie-breakers is fine).
<p>
<li>
Some areas will be easier to agree on than others.
Our priorities should be based on achieving as much
interoperability as possible if we can't attain perfection.
That is, it is better to end up with a few restrictions being required
for interoperable code, than to have no interoperability at all.
This suggests priorities as follows:
<ol>
<li> Items requiring base ABI changes that might affect other
languages, and will therefore become impossible soon.
Examples include exception handling / stack unwind,
or ELF changes (not extensions).
<li> Core features where differences will prevent virtually any
C++ object code from porting.
Examples include data layout and calling conventions.
<li> Limited usage features,
where users can achieve portability by avoiding the feature.
An example might be multi-threading.
<li> Peripheral features,
where the requirements on users to achieve
portability are clear and easy to implement.
An example is non-explicit inlining,
where compilers would presumably allow it to just be suppressed.
<li> Tool interfaces, which affect how users build code,
rather than what they build.
An example is the compilation command line.
</ol>
<p>
<li>
Mechanisms/methods which allow coexistence of incompatible
implementations may be suitable in some cases.
For instance, packaging vendor-specific compiler support runtimes
in DSOs occupying distinct namespaces might allow multiple such DSOs to
be loaded for mixed objects and avoid requiring that all vendors have
the same support runtimes.
</ul>
<p>
<hr>
<p>
<h4> Action Item Status </h4>
<p>
<table border=on cellpadding=3>
<tr>
<th> # </th>
<th> Action </th>
<th> Who </th>
<th> Status </th>
<th> Opened </th>
<th> Closed </th>
</tr>
<tr> <td> 1 </td>
<td> Distribute Sun C++ ABI </td>
<td> Mike Ball </td>
<td> open </td>
<td> 990603 </td>
<td> </td>
</tr>
<tr> <td> 2 </td>
<td> Distribute Sun C++ ABI Rationale </td>
<td> Mike Ball </td>
<td> open </td>
<td> 990603 </td>
<td> </td>
</tr>
<tr> <td> 3 </td>
<td> Distribute Taligent C++ ABI </td>
<td> Cary Coutant </td>
<td> open </td>
<td> 990603 </td>
<td> </td>
</tr>
<tr> <td> 4 </td>
<td> Expedite IA-64 RT Arch doc release </td>
<td> Cary Coutant </td>
<td> open </td>
<td> 990603 </td>
<td> </td>
</tr>
<tr> <td> 5 </td>
<td> Set up n-way NDA for eligible members </td>
<td> Priti Shrivastav </td>
<td> open </td>
<td> 990603 </td>
<td> </td>
</tr>
<tr> <td> 6 </td>
<td> Organize/summarize object layout issues and alternatives </td>
<td> Matt Austern </td>
<td> open </td>
<td> 990603 </td>
<td> </td>
</tr>
</table>
<p>
<hr>
<p>
<h4> Issue Status </h4>
In the following table,
the <b><i>class</i></b> column attempts to classify the issue on the
basis of what it likely affects.
The identifiers used are:
<table>
<tr> <td> call </td>
<td> Function call interface, i.e. call linkage </td>
</tr>
<tr> <td> data </td>
<td> Data layout </td>
</tr>
<tr> <td> lib </td>
<td> Runtime library support </td>
</tr>
<tr> <td> lif </td>
<td> Library interface, i.e. API </td>
</tr>
<tr> <td> g </td>
<td> Potential gABI impact </td>
</tr>
<tr> <td> ps </td>
<td> Potential psABI impact </td>
</tr>
<tr> <td> source </td>
<td> Source code conventions (i.e. API, not ABI) </td>
</tr>
<tr> <td> tools </td>
<td> May affect how program construction tools interact </td>
</tr>
</table>
<p>
<hr width=50%>
<p>
<table border=on cellpadding=3>
<tr>
<th> # </th>
<th> Issue </th>
<th> Class </th>
<th> Status </th>
<th> Source </th>
<th> Opened </th>
<th> Closed </th>
</tr>
<tr> </tr>
<tr> <th> A </th>
<th colspan=6> <a href=issues-C++-layout.html> Object Layout </a> </th>
</tr>
<tr> <td> A-1 </td>
<td> Virtual function table </td>
<td> data </td>
<td> open </td>
<td> SGI </td>
<td> 990520 </td>
<td> </td>
</tr>
<tr> <td> A-2 </td>
<td> Virtual base classes </td>
<td> data </td>
<td> open </td>
<td> SGI </td>
<td> 990520 </td>
<td> </td>
</tr>
<tr> <td> A-3 </td>
<td> Multiple inheritance </td>
<td> data </td>
<td> open </td>
<td> SGI </td>
<td> 990520 </td>
<td> </td>
</tr>
<tr> <td> A-4 </td>
<td> Empty base classes </td>
<td> data </td>
<td> open </td>
<td> SGI </td>
<td> 990520 </td>
<td> </td>
</tr>
<tr> <td> A-5 </td>
<td> Empty parameters </td>
<td> data </td>
<td> open </td>
<td> SGI </td>
<td> 990520 </td>
<td> </td>
</tr>
<tr> <td> A-6 </td>
<td> RTTI (<code>type_info</code>) .o representation </td>
<td> data call ps </td>
<td> open </td>
<td> SGI </td>
<td> 990520 </td>
<td> </td>
</tr>
<tr> <td> A-7 </td>
<td> Vptr sharing with primary base class </td>
<td> data </td>
<td> open </td>
<td> HP </td>
<td> 990603 </td>
<td> </td>
</tr>
<tr> <td> A-8 </td>
<td> (Virtual) base class alignment </td>
<td> data </td>
<td> open </td>
<td> HP </td>
<td> 990603 </td>
<td> </td>
</tr>
<tr> <td> A-9 </td>
<td> Sorting fields as allowed by [class.mem]/12 </td>
<td> data </td>
<td> open </td>
<td> HP </td>
<td> 990603 </td>
<td> </td>
</tr>
<tr> <td> A-10 </td>
<td> Parameter struct field promotion </td>
<td> call </td>
<td> open </td>
<td> HP </td>
<td> 990603 </td>
<td> </td>
</tr>
<tr> <td> A-11 </td>
<td> Representation of pointers to members </td>
<td> data </td>
<td> open </td>
<td> Sun </td>
<td> 990603 </td>
<td> </td>
</tr>
<tr> </tr>
<tr> <th> B </th>
<th colspan=6> <a href=issues-C++-layout.html#vfunc>
Virtual Function Handling </a> </th>
</tr>
<tr> <td> B-1 </td>
<td> Adjustment of "this" pointer (e.g. thunks) </td>
<td> data call </td>
<td> open </td>
<td> SGI </td>
<td> 990520 </td>
<td> </td>
</tr>
<tr> <td> B-2 </td>
<td> Covariant return types </td>
<td> call </td>
<td> open </td>
<td> SGI </td>
<td> 990520 </td>
<td> </td>
</tr>
<tr> <td> B-3 </td>
<td> Allowed caching of vtable contents </td>
<td> call </td>
<td> open </td>
<td> HP </td>
<td> 990603 </td>
<td> </td>
</tr>
<tr> <td> B-4 </td>
<td> Function descriptors in vtable </td>
<td> data </td>
<td> open </td>
<td> HP </td>
<td> 990603 </td>
<td> </td>
</tr>
<tr> <td> B-5 </td>
<td> Where are vtables emitted? </td>
<td> data </td>
<td> open </td>
<td> HP </td>
<td> 990603 </td>
<td> </td>
</tr>
<tr> </tr>
<tr> <th> C </th>
<th colspan=6> Object Construction/Destruction </th>
</tr>
<tr> <td> C-1 </td>
<td> Interaction with .init/.fini </td>
<td> lif ps </td>
<td> open </td>
<td> SGI </td>
<td> 990520 </td>
<td> </td>
</tr>
<tr> <td> C-2 </td>
<td> Order of const/destr w.r.t. link </td>
<td> lif ps </td>
<td> open </td>
<td> HP </td>
<td> 990603 </td>
<td> </td>
</tr>
<tr> <td> C-3 </td>
<td> Order of const/destr w.r.t. DSOs </td>
<td> ps </td>
<td> open </td>
<td> HP </td>
<td> 990603 </td>
<td> </td>
</tr>
<tr> <td> C-4 </td>
<td> Calling vfuncs in constr/destr </td>
<td> call </td>
<td> open </td>
<td> Sun </td>
<td> 990603 </td>
<td> </td>
</tr>
<tr> <td> C-5 </td>
<td> Calling virtual destructors </td>
<td> call </td>
<td> open </td>
<td> Sun </td>
<td> 990603 </td>
<td> </td>
</tr>
<tr> <td> C-6 </td>
<td> Extra parameters to constr/destr </td>
<td> call </td>
<td> open </td>
<td> Cygnus </td>
<td> 990603 </td>
<td> </td>
</tr>
<tr> <td> C-7 </td>
<td> Extra parameters to constr/destr </td>
<td> call </td>
<td> open </td>
<td> Cygnus </td>
<td> 990603 </td>
<td> </td>
</tr>
<tr> </tr>
<tr> <th> D </th>
<th colspan=6> Exception Handling </th>
<ul>
<tr> <td> D-1 </td>
<td> Language-specific data area format </td>
<td> lib ps </td>
<td> open </td>
<td> SGI </td>
<td> 990520 </td>
<td> </td>
</tr>
<tr> <td> D-2 </td>
<td> Unwind personality routines </td>
<td> lib ps </td>
<td> open </td>
<td> SGI </td>
<td> 990520 </td>
<td> </td>
</tr>
<tr> <td> D-3 </td>
<td> Unwind process clarification </td>
<td> lib ps </td>
<td> open </td>
<td> SGI </td>
<td> 990520 </td>
<td> </td>
</tr>
<tr> <td> D-4 </td>
<td> Unwind routines nested? </td>
<td> lib ps </td>
<td> open </td>
<td> SGI </td>
<td> 990520 </td>
<td> </td>
</tr>
<tr> <td> D-5 </td>
<td> Interaction with other languages (e.g. Java) </td>
<td> lib ps </td>
<td> open </td>
<td> HP </td>
<td> 990603 </td>
<td> </td>
</tr>
<tr> <td> D-6 </td>
<td> Allow resumption in other languages? </td>
<td> lib ps </td>
<td> open </td>
<td> HP </td>
<td> 990603 </td>
<td> </td>
</tr>
<tr> <td> D-7 </td>
<td> Interaction with signals or asynch events </td>
<td> lib ps </td>
<td> open </td>
<td> HP </td>
<td> 990603 </td>
<td> </td>
</tr>
<tr> <td> D-8 </td>
<td> Interaction with threads packages </td>
<td> lib ps </td>
<td> open </td>
<td> SGI </td>
<td> 990603 </td>
<td> </td>
</tr>
<tr> </tr>
<tr> <th> E </th>
<th colspan=6> Template Instantiation Model </th>
</tr>
<tr> <td> E-1 </td>
<td> When does instantiation occur? </td>
<td> tools </td>
<td> open </td>
<td> SGI </td>
<td> 990520 </td>
<td> </td>
</tr>
<tr> <td> E-2 </td>
<td> Separate compilation model </td>
<td> tools </td>
<td> open </td>
<td> SGI </td>
<td> 990520 </td>
<td> </td>
</tr>
<tr> <td> E-3 </td>
<td> Template repository </td>
<td> tools </td>
<td> open </td>
<td> HP </td>
<td> 990603 </td>
<td> </td>
</tr>
<tr> </tr>
<tr> <th> F </th>
<th colspan=6> Name Mangling </th>
</tr>
<tr> <td> F-1 </td>
<td> Mangling convention </td>
<td> call </td>
<td> open </td>
<td> SGI </td>
<td> 990520 </td>
<td> </td>
</tr>
<tr> <td> F-2 </td>
<td> Mangled name size </td>
<td> call g </td>
<td> open </td>
<td> SGI </td>
<td> 990520 </td>
<td> </td>
</tr>
<tr> <td> F-3 </td>
<td> Distinguish template instantiation and specialization
</td>
<td> call g </td>
<td> open </td>
<td> SGI </td>
<td> 990520 </td>
<td> </td>
</tr>
<tr> </tr>
<tr> <th> G </th>
<th colspan=6> Miscellaneous </th>
</tr>
<tr> <td> G-1 </td>
<td> Basic command line options </td>
<td> tools </td>
<td> open </td>
<td> HP </td>
<td> 990603 </td>
<td> </td>
</tr>
<tr> <td> G-2 </td>
<td> Detection of 1-def rule violations </td>
<td> call </td>
<td> open </td>
<td> Sun </td>
<td> 990603 </td>
<td> </td>
</tr>
<tr> <td> G-3 </td>
<td> Inlined routine linkage </td>
<td> call </td>
<td> open </td>
<td> Sun </td>
<td> 990603 </td>
<td> </td>
</tr>
<tr> <td> G-4 </td>
<td> Dynamic init of local static objects and multithreading </td>
<td> call </td>
<td> open </td>
<td> SCO </td>
<td> 990607 </td>
<td> </td>
</tr>
</table>
<p>
<hr>
<p>
<h4>Notes from 3 June 1999 </h4>
<ul>
<p>
<li> Introductions
<p>
<li> Objectives: see above
<p>
<li> Procedure
<ul>
<li> Meetings: 10-12 Thursdays at SGI for the near term.
<li> Intel NDA: Generally unnecessary. Priti will set up n-way
for eligible members for cases where needed. Cary expects RT
architecture/software conventions document to be released in the
next month or two, removing most of the issues.
<li> Communication: Use of reflector encouraged for discussion.
NDA communication will be handled with password-protected PDF
once Intel sets up n-way.
<li> Available documents: Parties with existing, relevant documents
(includes Sun, HP) will send them to group.
<li> Intellectual property: Participants don't expect problems with
release of any of their IP. Microsoft has extensive patents in
the area, but they are excessively broad (covering obvious ideas
and prior art), so expectation is that they are not a problem.
Nonetheless, we should be aware of them.
</ul>
<p>
<li> Issue Identification: new issues reflected in status table.
</ul>
<p>
<hr>
<p>
Please send corrections to <a href=mailto:dehnert@xxxxxxx>Jim Dehnert</a>.
</BODY>
</HTML>
|
