Duncan Sands wrote:> Hi, > > >> Bitcode generated by llvm-ld with –disable-opt and –basiccg options is: >> > > ... > > > >> My point is why is the call to foo not resolved correctly in llvm-ld. >> > > Resolving an call to a direct call is an optimization. But you turned all > optimizations off. >How can we just selectively turn only that optimization ON? We don't want to turn on a whole lot of other stuff that instcombine does as they mess up debugging in our case. - Sanjiv> Ciao, > > Duncan. > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >
Hi Sanjiv,> How can we just selectively turn only that optimization ON?you can't. That said, you could write your own pass that does it.> We don't want to turn on a whole lot of other stuff that instcombine > does as they mess up debugging in our case.If instcombine makes debug info useless, then that's rather bad. Can you please explain more about this. Ciao, Duncan.
Duncan Sands wrote:> Hi Sanjiv, > >> How can we just selectively turn only that optimization ON? > > you can't. That said, you could write your own pass that does it. > >> We don't want to turn on a whole lot of other stuff that instcombine >> does as they mess up debugging in our case. > > If instcombine makes debug info useless, then that's rather bad. Can > you please explain more about this.multiple loads/stores to individual bitfields of a type are combined into single load/store and there are no generated code for certain C statements.> > Ciao, > > Duncan.