Displaying 4 results from an estimated 4 matches for "endresult".
2018 Jan 25
2
llvm::UpgradeDebugInfo does a full verification
..., buggy versions of LLVM, or buggy frontends) that would crash LLVM. The "upgrade" consists of stripping the debug info form the module.
Yeah I read that. My problem is that I use these calls to feed llvm my
generated bitcode (I don't use the llvm apis, I write bitcode and give
the endresult to llvm); now there's a fairly noticable overhead in
loading this code into llvm and there doesn't seem to be a "load bitcode
and skips checks" call I can use instead.
2018 Jan 25
0
llvm::UpgradeDebugInfo does a full verification
...versions of LLVM, or buggy frontends) that would crash LLVM. The "upgrade" consists of stripping the debug info form the module.
>
> Yeah I read that. My problem is that I use these calls to feed llvm my generated bitcode (I don't use the llvm apis, I write bitcode and give the endresult to llvm); now there's a fairly noticable overhead in loading this code into llvm and there doesn't seem to be a "load bitcode and skips checks" call I can use instead.
For testing purposes, opt and llc provide an option to not run the Verifier, but want to strongly discourage usi...
2018 Jan 24
2
llvm::UpgradeDebugInfo does a full verification
Hi,
I noticed that since recently UpgradeDebugInfo (Which is called for
loading any bitcode from disk/memory) does a full bitcode verification.
Is this on purpose or is this a mistake? Seems to have a fair amount of
overhead.
2018 Jan 24
0
llvm::UpgradeDebugInfo does a full verification
> On Jan 23, 2018, at 11:01 PM, Carlo Kok via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>
> Hi,
>
> I noticed that since recently UpgradeDebugInfo (Which is called for loading any bitcode from disk/memory) does a full bitcode verification. Is this on purpose or is this a mistake? Seems to have a fair amount of overhead.
That is be design, though there are bugs in the LTO