arm64: print '0x' before hex values

[christos]

Summary

Not making it explicit that we're printing values in hex can be
misleading when the number doesn't contain hex-only symbols (a-f). A
good example of this is print_gp_register(), where we print "(func +
offset)"; if the offset doesn't contain a-f symbols, it's not
immediately clear if that value is in decimal or hex.

[christos]

Forgot some printfs.

[christos]

Use '0x' instead of '#', fix width issues.

[imp]

What was wrong with #? We use it all over the place.

[christos]

In D40583#924040, @imp wrote:

What was wrong with #? We use it all over the place.

It doesn't print '0x' if the value is 0, and it also messes up column alignment. We could replace '0x' with '#' wherever we do not care about alignment, if you insist, however.

[imp]

In D40583#924043, @christos wrote:

In D40583#924040, @imp wrote:

What was wrong with #? We use it all over the place.

It doesn't print '0x' if the value is 0, and it also messes up column alignment. We could replace '0x' with '#' wherever we do not care about alignment, if you insist, however.

Ah, I didn't know that detail. That's a decent enough reason to just be consistent.

[markj]

Approved.

It doesn't print '0x' if the value is 0, and it also messes up column alignment.

I would mention this in the commit log.