On Fri, 30 Dec 2011, Michael Meissner wrote:
> I udpated the powerpc changes in the GCC 4.7 summary:
Thanks, Michael! I just realized that I had not made two editorial
changes I spotted at that time. Done now. Better late than never. :-)
On the following I am not sure how to best go about, but somehow
this appears a bit confusing (to me at least ;-). Can you think
of a way to make this more clear to "regular" users?
+ <li>The powerpc will now enable machine specific builtin functions when
+ the user switches the target machine using the
+ <code>#pragma GCC target</code> or <code>GCC target attribute</code>
+ code sequences. In additon, the target macros are updated.
Gerald
Index: changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.7/changes.html,v
retrieving revision 1.113
diff -u -3 -p -r1.113 changes.html
--- changes.html 5 Jun 2012 11:03:53 -0000 1.113
+++ changes.html 10 Jun 2012 21:26:10 -0000
@@ -808,7 +808,7 @@ void set_portb (uint8_t value)
<ul>
<li>Vectors of type <i>vector long long</i> or <i>vector long</i> are
passed and returned using the same method as other vectors with the VSX
- instruction set. Previously the GCC compiler did not adhere to the ABI
+ instruction set. Previously GCC did not adhere to the ABI
for 128-bit vectors with 64-bit integer base types (PR 48857).
This will also be fixed in the GCC 4.6.1 and 4.5.4 releases.</li>
@@ -826,8 +826,8 @@ void set_portb (uint8_t value)
pointer a lot, but it can slow down other functions that only call
through a function pointer in exceptional cases.</li>
- <li>The PowerPC port will now enable machine-specific builtin functions
- when the user switches the target machine using the
+ <li>The PowerPC port will now enable machine-specific built-in
+ functions when the user switches the target machine using the
<code>#pragma GCC target</code> or
<code>__attribute__ ((__target__ ("<em>target</em>")))</code>
code sequences. In additon, the target macros are updated.
