[LLVMdev] bit code file incompatibility due to debug info changes

Chandler Carruth chandlerc at google.com
Mon Nov 18 10:37:06 PST 2013


On Mon, Nov 18, 2013 at 10:35 AM, Eric Christopher <echristo at gmail.com>wrote:

> >> At a minimum, it seems like we need a version number in the debug info
> >> metadata so we can detect this situation and avoid crashing.
> >
> >
> > Or to put it in the terms of the IR: we need to autoupgrade the debug
> info
> > metadata just like we do intrinsics. With debug info this might (at the
> > worst) involve dropping old metadata.
> >
>
> The verifier is probably the best route here. I think if we fail debug
> info verification we can just strip it and continue.


I'm slightly worried about relying on verification based "autoupgrade"
(where by upgrade I mean discard old cruft since it doesn't impact
correctness) due to compile time costs, but if the verification is fast
enough to be "always on", then cool.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131118/e5d344f0/attachment.html>


More information about the llvm-dev mailing list