[llvm-dev] CloneFunction during LTO leads to seg fault?
Scott A. Carr via llvm-dev
llvm-dev at lists.llvm.org
Tue Feb 9 11:03:13 PST 2016
Thanks for you reply. Here is the full output of -print-after-all 
and just the module itself after my pass.
I've looked over the IR, but I can't see anything obviously wrong.
I'm not sure what you meant by:
> You may want to try to add it at the end of the pipeline
My pass is the last one added inside populateLTOPassManager. Should I
add it to the PassManager somewhere else?
On 02/09/2016 01:36 PM, Mehdi Amini wrote:
>> On Feb 9, 2016, at 10:24 AM, Scott A. Carr via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>> I'm writing an LTO pass and I'd like to be able to duplicate a function (with debugging info). I'm trying to accomplish this with CloneFunction but it's leading to a seg fault in ld.
>> I've whittled down my problem so that it occurs in this small pass .
>> If I run this pass with opt, I get the expected result (i.e. a valid program that calls main twice). If I run the pass during LTO, ld seg faults. Here is a pastebin of when ld seg faults in lldb .
>> If I set the third parameter of CloneFunction (ModuleLevelChanges) to false, then then compilation will complete -- but I lose debugging information in the cloned function. I really want to preserve the debug info.
>> Any idea what is wrong? Is this a bug? Usually when I screw up the module the verifier catches the problem. This is getting to I think CodeGen then crashing.
> What could help is to pass -mllvm -print-after-all to ld and get the IR before and after your pass ran, and also just before CodeGen.
>> I've found that the module itself needs to be non-trivial to cause the crash. Here is the module I'm testing with .
>> In case it is relevant: to get my pass to run during LTO I added "PM.add(createHelloPass())" to PassMangerBuilder::populateLTOPassManager. I'm using binutils-gold on Linux (Ubuntu 14.04 LTS).
> You may want to try to add it at the end of the pipeline, in case something does not play well with optimizations (just trying to pinpoint where the issue is).
More information about the llvm-dev