tree 142f0bb7808a660eda7c0aab0e4917dc3644e517
parent a8f9114b901cc648adc203b7d2ad0cc86573c8c2
author Derek Schuff <dschuff@chromium.org> 1707335479 -0800
committer Copybara-Service <copybara-worker@google.com> 1707335742 -0800

[Object][Wasm] Use file offset for section addresses in linked wasm files (#80529)

Wasm has no unified virtual memory space as other object formats and
architectures do, so previously WasmObjectFile reported 0 for all
section addresses, and until 428cf71ff used section offsets for function
symbols. Now we use file offsets for function symbols, and this change
switches section addresses to do the same (in linked files). The main
result of this is that objdump now reports VMAs in section listings, and
also uses file offets rather than section offsets when disassembling
linked binaries (matching the behavior of other disassemblers and stack
traces produced by browwsers). To make this work, this PR also updates
objdump's generation of synthetics fallback symbols to match lib/Object
and also correctly plumbs symbol types for regular and dummy symbols
through to the backend to avoid needing special knowledge of address 0.

This also paves the way for generating symbols from name sections rather
than symbol tables or imports (see #76107) by allowing the
disassembler's synthetic fallback symbols match the name-section
generated symbols (in a followup PR).

GitOrigin-RevId: 8b0f47bfa4b6aa1bafa10261444c93aba5a2d31d