2 Commits

Author	SHA1	Message	Date
Peter Collingbourne	028eb5a3f8	Bitcode: Change reader interface to take memory buffers. ... As proposed on llvm-dev: http://lists.llvm.org/pipermail/llvm-dev/2016-October/106595.html This change also fixes an API oddity where BitstreamCursor::Read() would return zero for the first read past the end of the bitstream, but would report_fatal_error for subsequent reads. Now we always report_fatal_error for all reads past the end. Updated clients to check for the end of the bitstream before reading from it. I also needed to add padding to the invalid bitcode tests in test/Bitcode/. This is because the streaming interface was not checking that the file size is a multiple of 4. Differential Revision: https://reviews.llvm.org/D26219 llvm-svn: 285773	2016-11-02 00:08:19 +00:00
Filipe Cabecinhas	ecf8f7f49b	[Bitcode reader] Fix a few assertions when reading invalid files ... Summary: When creating {insert,extract}value instructions from a BitcodeReader, we weren't verifying the fields were valid. Bugs found with afl-fuzz Reviewers: rafael Subscribers: llvm-commits Differential Revision: http://reviews.llvm.org/D7325 llvm-svn: 229345	2015-02-16 00:03:11 +00:00