Potentially merging the transactional-memory branch into mainline.

Aldy Hernandez aldyh@redhat.com
Mon Nov 7 21:48:00 GMT 2011


> Could you please fix up whitespace in the patch, at least leading tabs
> and trailing whitespace?
> On the patch it is easy to do, something like:
> sed 's/^+\([\t]*\) \{64\}/+\1\t\t\t\t\t\t\t\t/;s/^+\([\t]*\) \{32\}/+\1\t\t\t\t/;s/^+\([\t]*\) \{16\}/+\1\t\t/;s/^+\([\t]*\) \{8\}/+\1\t/;s/^+\(.*[^[:blank:]]\)[[:blank:]]\+$/+\1/;s/^+[[:blank:]]\+$/+/' patch>  patch.whitespace
> and then interdiff patch patch.whitespace>  whitespace
> and review that diff and if appropriate commit to branch before merging?

Easy only for the keepers of incomprehensible sed magic!  Thanks for the 
script.

Here is the toplevel ChangeLog.tm entry.

	* Fix leading tabs and trailing whitespace throughout entire
	branch.

Attached is the compressed patch I will commit after I do a full 
bootstrap and regtest, as I'm rather queasy of committing even 
whitespace changes right now.

This pretty much culminates my responses to reviews of the branch.  I 
will post a separate status report once the last three patches are 
approved (one from rth, one from Torvald, and one from myself).  I 
believe we have addressed everything that was a blocker.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: curr.gz
Type: application/x-gzip
Size: 36481 bytes
Desc: not available
URL: <https://gcc.gnu.org/pipermail/gcc/attachments/20111107/c07e0a75/attachment.bin>


More information about the Gcc mailing list