summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Support/BinaryStreamReader.cpp
diff options
context:
space:
mode:
authorBob Haarman <llvm@inglorion.net>2017-05-25 21:12:15 +0000
committerBob Haarman <llvm@inglorion.net>2017-05-25 21:12:15 +0000
commit55256ada254f08bd86b4baa912eb1339af205ed6 (patch)
tree66305e1280859e5604fb9fabf538260b5c7f6279 /llvm/lib/Support/BinaryStreamReader.cpp
parentc4e4b7e31e8efc917352286aa6e22d78b659d44d (diff)
downloadbcm5719-llvm-55256ada254f08bd86b4baa912eb1339af205ed6.tar.gz
bcm5719-llvm-55256ada254f08bd86b4baa912eb1339af205ed6.zip
[pdb] pad source file name buffer at the end instead of the beginning
Summary: DbiStreamBuilder calculated the offset of the source file names inside the file info substream as the size of the file info substream minus the size of the file names. Since the file info substream is padded to a multiple of 4 bytes, this caused the first file name to be aligned on a 4-byte boundary. By contrast, DbiModuleList would read the file names immediately after the file name offset table, without skipping to the next 4-byte boundary. This change makes it so that the file names are written to the location where DbiModuleList expects them, and puts any necessary padding for the file info substream after the file names instead of before it. Reviewers: amccarth, rnk, zturner Reviewed By: amccarth, zturner Subscribers: llvm-commits Differential Revision: https://reviews.llvm.org/D33475 llvm-svn: 303917
Diffstat (limited to 'llvm/lib/Support/BinaryStreamReader.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud