|
From: Kevin K. <kev...@gm...> - 2018-04-16 16:50:25
|
On Mon, Apr 16, 2018 at 8:24 AM, Donal K. Fellows <don...@ma...> wrote: >> I've probably overlooked something. This is where a second pair of >> eyeballs might come in handy. > > Indeed. (I'm guessing that the coro passes care because they're doing > surgery to the debug info. Which seems reasonable.) You're right, I was siphoning off the bitcode in LLVM::optimise (jit.tcl) in the 'dump-pre' step, which comes just before verifying the module. Once I'm in a place to do it, I'll move that after the 'verify' and report back. (It surely doesn't explain the crash in '$module optimize', which comes after verification and in any case finalizes the debug information, but getting the assembly and bitcode after the info is finalized might offer more insight.) |