Detect and merge tail blocks, preserve global-scope symbols #10
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
blr), these are merged back into the preceding function rather than treated as separate symbolsassert_eqon function end addresses to allow detected ends beyond pdata-reported ends (since tail blocks extend past pdata boundaries)symbols.txt, PDB, or map file), preserving intentionally defined functions that happen to look like tail blockswrite_symbols()would drop user-defined symbols on every re-split because merged tail blocks getNoWriteflagsExample:
Curl_resolv_timeoutThe MSVC compiler placed
Curl_resolv_timeout(7 instructions, 28 bytes) immediately afterCurl_resolvwith a tail call (b, notbl) back into it. Without this change, dtk merges the two andCurl_resolv_timeoutdisappears fromsymbols.txton every split, preventing independent comparison in objdiff.With this change and
scope:globalin symbols.txt:Curl_resolv: 94.5% → 99.9% (remaining 2 diffs are relocation encoding, unfixable)Curl_resolv_timeout: 100% matchTest plan
cargo build --release— compiles clean