Name packed relocations section appropriately for arm64.

Name packed relocations section appropriately for arm64.

Arm uses .rel.dyn, and arm64 .rela.dyn.  For consistency, name the
packed relocations section as '.android.rela.dyn' for arm64, and
leave '.android.rel.dyn' for arm32.

[ No semantic effect, since packing and unpacking tools treat both
section names identically, and use the signature at the start of
section data to indicate content type. ]

BUG=385553
Committed: https://crrev.com/1ddabff1f7612387b7578d3855cb5ba9729de9f2
Cr-Commit-Position: refs/heads/master@{#298515}

[simonb (inactive), 2014-10-07 13:41:37]

simonb@chromium.org changed reviewers:
+ rmcilroy@chromium.org

[rmcilroy, 2014-10-07 14:02:39]

https://codereview.chromium.org/635863002/diff/1/build/android/gyp/pack_arm_r...
File build/android/gyp/pack_arm_relocations.py (right):

https://codereview.chromium.org/635863002/diff/1/build/android/gyp/pack_arm_r...
build/android/gyp/pack_arm_relocations.py:48: new_section = '.android.rel.dyn'
This seems a bit hacky to work out if it's 32 or 64.  Could we just pass this in
as an argument instead and use the target_arch variable in gyp to decide on what
name to pass to the too instead?

[simonb (inactive), 2014-10-07 15:34:20]

https://codereview.chromium.org/635863002/diff/1/build/android/gyp/pack_arm_r...
File build/android/gyp/pack_arm_relocations.py (right):

https://codereview.chromium.org/635863002/diff/1/build/android/gyp/pack_arm_r...
build/android/gyp/pack_arm_relocations.py:48: new_section = '.android.rel.dyn'
On 2014/10/07 14:02:39, rmcilroy wrote:
> This seems a bit hacky to work out if it's 32 or 64.  Could we just pass this
in
> as an argument instead and use the target_arch variable in gyp to decide on
what
> name to pass to the too instead?

Done.  Updated version in patch set 2.  PTAL, thanks.

[rmcilroy, 2014-10-07 15:58:19]

lgtm, thanks.

[simonb (inactive), 2014-10-07 16:02:39]

The CQ bit was checked by simonb@chromium.org

[commit-bot: I haz the power, 2014-10-07 16:03:38]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/635863002/20001

[commit-bot: I haz the power, 2014-10-07 17:30:44]

Committed patchset #2 (id:20001) as 875cafa91fccb74ebaac5979e80dd3f8692de158

[commit-bot: I haz the power, 2014-10-07 17:31:29]

Patchset 2 (id:??) landed as
https://crrev.com/1ddabff1f7612387b7578d3855cb5ba9729de9f2
Cr-Commit-Position: refs/heads/master@{#298515}