Remove gcc 3.3 ABI hack task--we did the 3.2 gcc release task, but it's

too late in the release cycle to hack the C++ ABI.  Oh well.

Chown the gbde documentation task to chris@, since he has a WIP.
This commit is contained in:
Robert Watson 2002-12-19 01:40:41 +00:00
parent 3282140264
commit c2a0072854
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/www/; revision=15382

View file

@ -1,7 +1,7 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [ <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY base CDATA "../.."> <!ENTITY base CDATA "../..">
<!ENTITY email 'freebsd-qa'> <!ENTITY email 'freebsd-qa'>
<!ENTITY date "$FreeBSD: www/en/releases/5.0R/todo.sgml,v 1.114 2002/12/19 01:37:17 rwatson Exp $"> <!ENTITY date "$FreeBSD: www/en/releases/5.0R/todo.sgml,v 1.115 2002/12/19 01:39:16 rwatson Exp $">
<!ENTITY title "FreeBSD 5.0 Open Issues"> <!ENTITY title "FreeBSD 5.0 Open Issues">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes; <!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
<!ENTITY % developers SYSTEM "../../developers.sgml"> %developers; <!ENTITY % developers SYSTEM "../../developers.sgml"> %developers;
@ -242,16 +242,6 @@
"PIOCWAIT: Input/output error" occasionally on startup.</td> "PIOCWAIT: Input/output error" occasionally on startup.</td>
</tr> </tr>
<tr>
<td>gcc 3.3 ABI hack</td>
<td>--</td>
<td>&a.obrien;</td>
<td>Hack the C++ ABI in our in-tree version of g++ to match what
will be used for gcc 3.3. This would permit us forward
ABI compatibility, avoiding future breakage when we want to
import the new gcc 3.3 during 5.x lifetime.</td>
</tr>
<tr> <tr>
<td>Documentation rottage: S/Key</td> <td>Documentation rottage: S/Key</td>
<td>--</td> <td>--</td>
@ -263,7 +253,7 @@
<tr> <tr>
<td>Documentation wanted: gdbe</td> <td>Documentation wanted: gdbe</td>
<td>--</td> <td>--</td>
<td>--</td> <td>&.chris;</td>
<td>5.0 includes GDBE, supporting encryption of swap and storage. <td>5.0 includes GDBE, supporting encryption of swap and storage.
It would be nice if that was documented in the handbook.</td> It would be nice if that was documented in the handbook.</td>
</tr> </tr>