tree 9962ce39f0768d6c1dd7b239060a3c18eaa5faa3
parent 0147515fd20c86ee59e5b7be03f0e81f7e51f833
author Cherry Zhang <cherryyz@google.com> 1535939195 -0400
committer Cherry Zhang <cherryyz@google.com> 1540660817 +0000

bridge: attach metadata to address-taken allocas to help liveness analysis

The liveness of address-taken allocas and non-address-taken
allocas are different. To help the liveness analysis here we
attach some metadata to allocas if the frontend tells us it is
address-taken.

The backend could inspect the IR to see if an alloca's address
is taken. But this is sometimes too conservative. For example,
certain functions take the address just to read or write (e.g.
the equality function of an aggregate type). The frontend does
not mark the variable address-taken in this case. And it is safe
for the liveness to treat it as non-address-taken.

Change the local variables in the unit tests to be non-address-
taken, so we don't need to add the metadata to the expected
outputs. Even if the variable's address is actually taken, it
doesn't really matter, as the address-taken information is only
used for stack map generation, which does not run in these unit
tests.

Change-Id: Ia25326c72c0e9571f9072ccfdd26f25468a3fbd4
Reviewed-on: https://go-review.googlesource.com/c/137759
Reviewed-by: Than McIntosh <thanm@google.com>