code review 7369048: cmd/gc: avoid runtime code generation for closures

cmd/gc: avoid runtime code generation for closures

Change ARM context register to R7, to get out of the way
of the register allocator during the compilation of the
prologue statements (it wants to use R0 as a temporary).

Step 2 of http://golang.org/s/go11func.

[rsc, 2013-02-22 19:25:49]

Hello ken2 (cc: golang-dev@googlegroups.com),

I'd like you to review this change to
https://go.googlecode.com/hg/

[rsc, 2013-02-22 19:25:54]

*** Submitted as https://code.google.com/p/go/source/detail?r=51f7d979c6e8 ***

cmd/gc: avoid runtime code generation for closures

Change ARM context register to R7, to get out of the way
of the register allocator during the compilation of the
prologue statements (it wants to use R0 as a temporary).

Step 2 of http://golang.org/s/go11func.

R=ken2
CC=golang-dev
https://codereview.appspot.com/7369048

[rsc, 2013-02-22 20:24:54]

This broke Windows, as usual. I am looking into it.

[remyoudompheng, 2013-02-23 08:32:12]

On 2013/2/22  <rsc@golang.org> wrote:
> Description:
> cmd/gc: avoid runtime code generation for closures
>
> Change ARM context register to R7, to get out of the way
> of the register allocator during the compilation of the
> prologue statements (it wants to use R0 as a temporary).
>
> Step 2 of http://golang.org/s/go11func.
>
> Please review this at https://codereview.appspot.com/7369048/

Does it already make closure blobs eligible for escape analysis or do
we need a bit more work?

Rémy.