llvm-project

History

David Blaikie 8503565eec [opaque pointer type] bitcode support for explicit type parameter to the load instruction

Summary:
I've taken my best guess at this, but I've cargo culted in places & so
explanations/corrections would be great.

This seems to pass all the tests (check-all, covering clang and llvm) so I
believe that pretty well exercises both the backwards compatibility and common
(same version) compatibility given the number of checked in bitcode files we
already have. Is that a reasonable approach to testing here? Would some more
explicit tests be desired?

1) is this the right way to do back-compat in this case (looking at the number
  of entries in the bitcode record to disambiguate between the old schema and
  the new?)

2) I don't quite understand the logarithm logic to choose the encoding type of
  the type parameter in the abbreviation description, but I found another
  instruction doing the same thing & it seems to work. Is that the right
  approach?

Reviewers: dexonsmith

Differential Revision: http://reviews.llvm.org/D7655

llvm-svn: 230414

2015-02-25 01:07:20 +00:00

BitcodeReader.cpp

[opaque pointer type] bitcode support for explicit type parameter to the load instruction

2015-02-25 01:07:20 +00:00

BitcodeReader.h

Use common parse routine to read alignment values from bitcode

2015-02-22 19:32:03 +00:00

BitReader.cpp

Propagate a better error message to the C api.

2015-02-03 01:53:03 +00:00

BitstreamReader.cpp

Clean up some inappropriate choices of type in the bitcode reader. None of