Gerald Pfeifer writes:
> On Fri, 16 Mar 2012, Rainer Orth wrote:
>> While reading through the GCC 4.7 changes.html, I noticed a couple of
>> nits that this patch fixes. It's mostly wording and grammar changes (so
>> I may well be wrong and would appreciate a native speaker having a look
>
> This looks good in general, thanks.
>
> Instead of the change around pollution I would prefer
> "Avoid polluting the global namespace and do not include..."
> instead of either the old or the proposed version, though I'll admit
> I do not have a strong rationale.
I think you're right: it correctly emphasizes the avoidance.
> I am not sure about "The powerpc" vs "The PowerPC" vs "powerpc",
> please pass that part by David Edelsohn.
Already dealt with, thanks David.
> Similarly, are you sure "#pragma GCC target attribute"
> change is incorrect. Isn't that a function attribute?
Indeed: neither the original nor my patch were right here. I've updated
my patch to include the correct syntax.
Ok now?
Thanks.
Rainer
--
-
Rainer Orth, Center for Biotechnology, Bielefeld University
Index: changes.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.7/changes.html,v
retrieving revision 1.102
diff -u -p -r1.102 changes.html
--- changes.html 22 Mar 2012 09:40:43 - 1.102
+++ changes.html 22 Mar 2012 16:40:14 -
@@ -126,7 +126,7 @@
void foo(int a)
{
- if (a>10)
+ if (a > 10)
... huge code ...
}
void bar (void)
@@ -166,7 +166,7 @@ void bar (void)
GCC will now produce two copies of foo. One with flag being
true, while other with flag being
false. This leads to performance improvements previously
- possibly only by inlining all calls. Cloning causes a lot less code size
+ possible only by inlining all calls. Cloning causes a lot less code size
growth.
@@ -242,20 +242,21 @@ void foo (char *a, const char *b, const
Experimental support for transactional memory has been added.
- It includes support for the compiler, as well as a supporting
+ It includes support in the compiler, as well as a supporting
runtime library called libitm. To compile code
with transactional memory constructs, use
the -fgnu-tm option.
- Support is currently available for the x86-32, x86-64, and Alpha
- platforms.
+ Support is currently available for Alpha, ARM, PowerPC, SH, SPARC,
+ and 32-bit/64-bit x86 platforms.
For more details on transactional memory
- see http://gcc.gnu.org/wiki/TransactionalMemory";>here.
+ see http://gcc.gnu.org/wiki/TransactionalMemory";>the GCC
+ WiKi.
@@ -266,11 +267,11 @@ void foo (char *a, const char *b, const
existing __sync built-in routines.
- Atomic support is also available for memory blocks. Lock free
+ Atomic support is also available for memory blocks. Lock-free
instructions will be used if a memory block is the same size and
alignment as a supported integer type. Atomic operations which do not
- have lock free support are left as function calls. A set of library
- functions are available on the GCC atomic wiki in the "External
+ have lock-free support are left as function calls. A set of library
+ functions is available on the GCC atomic wiki in the "External
Atomics Library" section.
@@ -279,8 +280,8 @@ void foo (char *a, const char *b, const
- When a binary operation performed on vector types and one of the operands
- is a uniform vector it is possible to replace the vector with the
+ When a binary operation is performed on vector types and one of the operands
+ is a uniform vector, it is possible to replace the vector with the
generating element. For example:
typedef int v4si __attribute__ ((vector_size (16)));
@@ -352,7 +353,7 @@ struct B {
};
struct D : B {
- void f() const;// error: D::f attempts to override final B::f
+ void f() const;// error: D::f attempts to override final B::f
void f(long) override; // error: doesn't override anything
void f(int) override; // ok
};
@@ -499,7 +500,8 @@ well.
Added --enable-clocale=newlib configure option.
Debug Mode iterators for unordered associative containers.
- Avoid polluting the global namespace by inclusion of .
+ Avoid polluting the global namespace and do not include
+ .
@@ -509,7 +511,7 @@ well.
The compile flag http://gcc.gnu.org/onlinedocs/gcc-4.7.0/gfortran/Code-Gen-Options.html#index-g_t_0040code_007bfstack_002darrays_007d-254";
>-fstack-arrays has been added, which causes
- that all local arrays are put on stack memory. For some
+ all local arrays to be put
