[llvm-commits] [llvm] r146604 - in /llvm/trunk: lib/CodeGen/MachineSink.cpp test/CodeGen/ARM/2011-12-14-machine-sink.ll

[Anton Korobeynikov]

> One alternative for you is to reproduce segfault in debugger and investigate what is being compiled.
>
> Other alternative is to narrow down the particular MI sink that is difference maker. You can do this by disabling this patch and adding a artificial threshold in Machine Sink pass to control how many instructions are sinked. One you know the critical MI sink, you can investigate how it impacts other passes, including register allocator, down the road.
>
> I am afraid, there is not any easy answer.
Previously one could use bugpoint to reduce such problems
automatically via splitting the code into two parts, compiling one
part with gcc and another - via llvm.
Though, I doubt this will work right now since cbe is broken now. That
said, you do not have any automatic reduction in such cases and should
do everything by hands.

-- 
With best regards, Anton Korobeynikov
Faculty of Mathematics and Mechanics, Saint Petersburg State University