On 29/03/13 13:54, Tom de Vries wrote: > I split the patch up into 10 patches, to facilitate further review: > ... > 0001-Add-command-line-option.patch > 0002-Add-new-reg-note-REG_CALL_DECL.patch > 0003-Add-implicit-parameter-to-find_all_hard_reg_sets.patch > 0004-Add-TARGET_FN_OTHER_HARD_REG_USAGE-hook.patch > 0005-Implement-TARGET_FN_OTHER_HARD_REG_USAGE-hook-for-ARM.patch > 0006-Collect-register-usage-information.patch > 0007-Use-collected-register-usage-information.patch > 0008-Enable-by-default-at-O2-and-higher.patch > 0009-Add-documentation.patch > 0010-Add-test-case.patch > ... > I'll post these in reply to this email. >
Something went wrong with those emails, which were generated. I tested the emails by sending them to my work email, where they looked fine. I managed to reproduce the problem by sending them to my private email. It seems the problem was inconsistent EOL format. I've written a python script to handle composing the email, and posted it here using that script: http://gcc.gnu.org/ml/gcc-patches/2013-03/msg01311.html. Given that that email looks ok, I think I've addressed the problems now. I'll repost the patches. Sorry about the noise. Thanks, - Tom
