Message ID | CAEwic4Z8zvB2OpbyeK_Xpk4W=YpY1vR=0Ky8kCUm-3sw2ccApA@mail.gmail.com |
---|---|
State | New |
Headers | show |
On Thu, 1 Mar 2012, Kai Tietz wrote: > + <li>Windows mingw targets are using <code>-mms-bitfields</code> option > + as default.</li> "are using the" (add "the") and probably "by default" > + <li>Window x86 target is using <code>__thiscall</code> calling convention > + for C++ class-member functions.</li> "The Windows x86" or "Windows x86 targets are" (in any case, add "s" to "Window" :-). "the...calling convention" > + <li>Support of <code>--with-threads=posix</code> for Windows > mingw targets.</li> Is this a configure option? In that case I'd say "Support for the ... configure option..." to make this clear. Thanks for taking the time to write this up! The patch is fine with the above, or comparable changes. Gerald
Index: wwwdocs/htdocs/gcc-4.7/changes.html =================================================================== --- wwwdocs.orig/htdocs/gcc-4.7/changes.html +++ wwwdocs/htdocs/gcc-4.7/changes.html @@ -678,6 +678,11 @@ int add_values (const __flash int *p, in is available through <code>-march=core-avx-i</code>.</li> <li>Support for the new Intel processor codename Haswell with AVX2, FMA, BMI, BMI2, LZCNT is available through <code>-march=core-avx2</code>.</li> + <li>Windows mingw targets are using <code>-mms-bitfields</code> option + as default.</li> + <li>Window x86 target is using <code>__thiscall</code> calling convention + for C++ class-member functions.</li> + <li>Support of <code>--with-threads=posix</code> for Windows mingw targets.</li> <li>...</li>