[llvm-dev] Backward compatibility of LLVM IR - ll/bc files

Craig Topper via llvm-dev llvm-dev at lists.llvm.org
Sun Apr 26 22:18:28 PDT 2020


I thought the binary bitcode reader was backwards compatible already.
That's what is documented here
https://llvm.org/docs/DeveloperPolicy.html#ir-backwards-compatibility

~Craig


On Sun, Apr 26, 2020 at 9:29 PM Ehud Katz via llvm-dev <
llvm-dev at lists.llvm.org> wrote:

> Quite often I get to work on an old bug, where an old ll/bc file is
> attached as a testcase. These files, in most cases (if not all), need to be
> converted somehow to the latest format, for the trunk version to be able to
> parse it without an error.
>
>
> So a few questions arise:
>
> 1. Is there a standard way to convert an old ll/bc to the latest? If not,
> what is the common approach for these cases?
>
> 2. If there is no such tool, should we have one? (I think we should, of
> course.)
>
> 3. What about automatically let the ll and bc Readers do the conversion
> (internally)?
>
> 4. What about versions? Is there an RFC (probably old) for ll/bc file
> versioning? (I know there is an optional record for version in the bc file
> format, but it is not really utilized.)
>
>
> Cheers,
> Ehud.
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200426/cf236afc/attachment.html>


More information about the llvm-dev mailing list