read: don't use rnglists and loclists header #370
Merged
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.
These headers don't give information that is required for parsing
range lists or location lists, because the encoding of these lists
must match the encoding of the compilation unit.
Additionally, while the standard seems to indicate that each section
has only one of these headers, in practice this is not true.
Furthermore, when there are multiple headers, they do not have to
each have the same encoding, so our parsing was wrong in this case
because we only used the encoding from the first header.