Support newer versions of objdump #3
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.
Resolved incompatibilities with newer versions of
objdump. The most significant change seems to be the newly introduced behaviour whereobjdumpinterprets arbitrary long sequences of0x66bytes asdata32annotations. However, this does not seem to be valid according to the AMD manual norgcc. To allow crosschecking against newer versions, the cross-checking scripts strips out these annotations.Alternatively, we could extend the validator to output
data32annotations, but in that case we would have to perform some post-processing as well i.e. strip them or replace them with.byte 0x66in the input which is being fed togccduring cross-check.