| Message ID | 9173EF2E-B1B5-47F9-B2FC-AC992B7E06AF@sandoe-acoustics.co.uk |
|---|---|
| State | New |
| Headers | show |
On Feb 3, 2011, at 12:20 PM, IainS wrote: > Here is an initial stab at a changes entry for Darwin. > comments? Looks good to me...
On Thu, 3 Feb 2011, IainS wrote: > Here is an initial stab at a changes entry for Darwin. > comments? I was going to make some tweaks and commit the patch with you, but somehow I'm struggling with a number of overly long lines which break the patch. :-( Do you mind reformatting to avoid lines longer than some 76 columns? > Index: htdocs/gcc-4.6/changes.html > =================================================================== > + 'toll-free bridged' as per the Mac OSX system tools. Is there a specific reason to use single quotes? Otherwise I suggest to use double quotes. Is Mac OSX really the proper spelling or is there a blink before X missing? > + <li>The <code>-mdynamic-no-pic</code> option has been enabled</li> Full stop? > + Code supporting <code>-mdynamic-no-pic</code> optimization has been > added Something's wrong in terms of markup. You have a closing </li> and then a new sentence without an opening <li>? > + <li>The default value for <code>-mtune=</code> has been changed</li> > + Since Darwin systems are primarily Xeon, Core-2 or similar the default > tuning > + has been changed to <code>-mtune=core2</code>. Same here. In case you want to force a line break, use <br />, but put the </li> at the end of the itme. > + Several significant bugs have been fixed, such that GCC now produces > code > + compatible with the Darwin64 PowerPC ABI. </li> > + <li>libffi and boehm-gc</li> > + The Darwin ports of the <code>libffi</code> and <code>boehm-gc</code> > + libraries have been upgraded to include a Darwin64 implementation. > + This means that powerpc*-*-darwin9 platforms may now, for example, > build > + Java applications with <code>-m64</code> enabled. Same as above re </li>. When refering to the libraries, I don't think we need <code>...</code>. The patch looks fine with this changes, and Mike already nodded. When committing just watch out for messages from my validator script; it is possible I missed one or two details. Thanks, Gerald
Index: htdocs/gcc-4.6/changes.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.6/changes.html,v retrieving revision 1.103 diff -u -r1.103 changes.html --- htdocs/gcc-4.6/changes.html 3 Feb 2011 13:01:55 -0000 1.103 +++ htdocs/gcc-4.6/changes.html 3 Feb 2011 20:17:54 -0000 @@ -808,6 +808,53 @@ At the moment, Android support is enabled only for ARM.</li> </ul> +<h3 id="darwin">Darwin/Mac OSX</h3> + <ul> + <li>General</li> + <ul> + <li>Initial support for <code>CFString</code> types has been added.</li> + This allows GCC to build projects including the system <em>Core Foundation + </em> frameworks. The GCC Objective-C family supports <code>CFString</code> + 'toll-free bridged' as per the Mac OSX system tools. <code>CFString</code> + is also recognized in the context of <code>format</code> attributes and + arguments (see the documentation for <code>format</code> attributes for + limitations). At present, 8-bit character types are supported. + <li>LTO-support</li> + Darwin has benefited from ongoing work on LTO; support for it is now + stable and enabled by default. + <li>Object file size reduction</li> + The Darwin zeroed memory allocators have been re-written to make more use of + <code>.zerofill</code> sections. For non-debug code, this can reduce object + file size significantly. + </ul> + <li>x86 Architecture</li> + <ul> + <li>The <code>-mdynamic-no-pic</code> option has been enabled</ li> + Code supporting <code>-mdynamic-no-pic</code> optimization has been added + and is applicable to <code>-m32</code> builds. The compiler bootstrap uses + the option where appropriate. + <li>The default value for <code>-mtune=</code> has been changed</li> + Since Darwin systems are primarily Xeon, Core-2 or similar the default tuning + has been changed to <code>-mtune=core2</code>. + </ul> + <li>PPC Architecture</li> + <ul> + <li>Darwin64 ABI</li> + Several significant bugs have been fixed, such that GCC now produces code + compatible with the Darwin64 PowerPC ABI. + <li>libffi and boehm-gc</li>
Hi, Here is an initial stab at a changes entry for Darwin. comments? Iain + The Darwin ports of the <code>libffi</code> and <code>boehm-gc</ code> + libraries have been upgraded to include a Darwin64 implementation. + This means that powerpc*-*-darwin9 platforms may now, for example, build + Java applications with <code>-m64</code> enabled. + <li>Plug-in support has been enabled.</li> + <li>Section Anchors</li> + The re-write of the memory allocators allowed resolution of issues + preventing the use of section anchors. The <code>-fsection- anchors</code> + option is now available although, presently, not heavily tested. + </ul> + </ul> + <h3 id="solaris">Solaris 2</h3> <h4>New Features</h4> <ul>