llvm-project.git/llvm/test/Bitcode/Inputs/invalid-array-operand-encoding.bc, branch main Unnamed repository; edit this file 'description' to name the repository. Bitcode: Change reader interface to take memory buffers. 2016-11-02T00:08:19+00:00 Peter Collingbourne peter@pcc.me.uk 2016-11-02T00:08:19+00:00 028eb5a3f823c25e6c3040d300910e23ed69e788 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 
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
[BitstreamReader] Make sure the Array operand type is an encoding 2015-05-27T00:48:43+00:00 Filipe Cabecinhas me@filcab.net 2015-05-27T00:48:43+00:00 8cd99e9a5a13bc3f229dbabc9e8baa7b10568598 Bug found with AFL fuzz. llvm-svn: 238269 
Bug found with AFL fuzz.

llvm-svn: 238269