Re: [wwwdocs] gcc-4.8/changes.html: mention IRA and transactional memory

2013-11-25 Thread Gerald Pfeifer
On Mon, 20 May 2013, Aldy Hernandez wrote:
> I am committing the attached patch.

Thanks, Aldy.

I just noticed the casing of SPARC and a bit of an inconsistency
around IA-32, and committed the follow-up below (which also contains
one "back end" fix).

Gerald

Index: changes.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.8/changes.html,v
retrieving revision 1.123
diff -u -3 -p -r1.123 changes.html
--- changes.html16 Oct 2013 13:47:15 -  1.123
+++ changes.html26 Nov 2013 03:09:31 -
@@ -145,11 +145,11 @@ by this change.
GNU/Linux.
 A new local register allocator (LRA) has been implemented, which
 replaces the 26 year old reload pass and improves generated
-code quality.  For now it is active on the ia32 and x86-64
+code quality.  For now it is active on the IA-32 and x86-64
 targets.
 Support for transactional memory has been implemented on the
 following architectures: IA-32/x86-64, ARM, PowerPC, SH,
-Sparc, and Alpha.
+SPARC, and Alpha.
   
 
 
@@ -639,7 +639,7 @@ int i = A().f();  // error, f() requires
 http://gcc.gnu.org/wiki/FunctionMultiVersioning";>wiki for more
 information.
 
- The x86 backend has been improved to allow option
+ The x86 back end has been improved to allow option
 -fschedule-insns to work reliably.
 This option can be used to schedule instructions better and leads to
 improved performace in certain cases.


Re: [wwwdocs] gcc-4.8/changes.html: mention IRA and transactional memory

2013-05-20 Thread Aldy Hernandez



Okay after considering those questions.  And thanks for catching
and addressing this!



Thank you.

I am committing the attached patch.
Index: gcc-4.8/changes.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.8/changes.html,v
retrieving revision 1.116
diff -u -r1.116 changes.html
--- gcc-4.8/changes.html24 Apr 2013 15:14:26 -  1.116
+++ gcc-4.8/changes.html20 May 2013 16:36:37 -
@@ -143,6 +143,13 @@
-fsanitize=thread. Instructions will be instrumented to
detect data races. The ThreadSanitizer is available on x86-64
GNU/Linux.
+A new local register allocator has been implemented, which
+replaces the 26 year old reload pass and improves generated
+code quality.  For now it is active on the ia32 and x86-64
+targets.
+Support for transactional memory has been implemented on the
+following architectures: IA-32/x86-64, ARM, PowerPC, SH,
+Sparc, and Alpha.
   
 
 


Re: [wwwdocs] gcc-4.8/changes.html: mention IRA and transactional memory

2013-05-20 Thread Gerald Pfeifer

On Fri, 17 May 2013, Aldy Hernandez wrote:
Errr, how did we miss this?  Ok, I'm partly to blame for the lack of 
transactional memory in changes.html, but something as big as getting 
rid of reload?!


I guess I need to start being more of a nuisance again when it comes
to release notes / announcements. :-/


Would it be preferable to mention IRA in the target specific x86
section instead?  I figured it was an important enough change to 
warrant front-page coverage.


Agreed.  Two suggestions:


Index: htdocs/gcc-4.8/changes.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.8/changes.html,v
retrieving revision 1.116
diff -u -r1.116 changes.html
--- htdocs/gcc-4.8/changes.html 24 Apr 2013 15:14:26 -  1.116
+++ htdocs/gcc-4.8/changes.html 17 May 2013 17:49:19 -
@@ -143,6 +143,11 @@
-fsanitize=thread. Instructions will be instrumented to
detect data races. The ThreadSanitizer is available on x86-64
GNU/Linux.
+A new local register allocator has been implemented, which
+replaces the 26 year old reload pass and improves generated code
+quality on ia32 and x86-64 targets.

How about making this "...quality.  For now it is active on..."?  The
idea is to make it explicit that this is a general change, which just
is enabled on these two architectures for now.

+Support for transactional memory has been implemented on
+selected architectures.

Do you have a list?

Okay after considering those questions.  And thanks for catching
and addressing this!

Gerald


[wwwdocs] gcc-4.8/changes.html: mention IRA and transactional memory

2013-05-17 Thread Aldy Hernandez
Errr, how did we miss this?  Ok, I'm partly to blame for the lack of 
transactional memory in changes.html, but something as big as getting 
rid of reload?!


Would it be preferable to mention IRA in the target specific x86 section 
instead?  I figured it was an important enough change to warrant 
front-page coverage.


Is this OK?
Index: htdocs/gcc-4.8/changes.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.8/changes.html,v
retrieving revision 1.116
diff -u -r1.116 changes.html
--- htdocs/gcc-4.8/changes.html 24 Apr 2013 15:14:26 -  1.116
+++ htdocs/gcc-4.8/changes.html 17 May 2013 17:49:19 -
@@ -143,6 +143,11 @@
-fsanitize=thread. Instructions will be instrumented to
detect data races. The ThreadSanitizer is available on x86-64
GNU/Linux.
+A new local register allocator has been implemented, which
+replaces the 26 year old reload pass and improves generated code
+quality on ia32 and x86-64 targets.
+Support for transactional memory has been implemented on
+selected architectures.