This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Potentially merging the transactional-memory branch into mainline.



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?

Jakub

[sorry for the duplicate, replying all this time]


Is this necessary for the entire patch, or just the parts that touch existing parts of the toolchain. For example, do you want me to run this on libitm/, etc? I'm really trying to minimize changes (even whitespace stuff) at the last minute, but if you think it's imperative, I will do so.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]