search for: getcost

Displaying 12 results from an estimated 12 matches for "getcost".

2017 Sep 16
3
RFC: Use closures to delay construction of optimization remarks
...<< NV("Callee", Callee) << " not inlined into " Transforms/IPO/Inliner.cpp- << NV("Caller", Caller) << " because too costly to inline (cost=" Transforms/IPO/Inliner.cpp- << NV("Cost", IC.getCost()) Transforms/IPO/Inliner.cpp- << ", threshold=" << NV("Threshold", IC.getThreshold()) << ")"); Then inside ORE we return right away if the remarks for the given pass is not enabled. This is nice and concise however there is still some o...
2013 Dec 16
3
[LLVMdev] [RFC] Iterrative compilation framework for Clang/LLVM
...r function, at these points decisions are made whether to execute default actions (as compiler would do without this framework) or to follow alternative paths. Let us consider Inliner example: Original code: if (!IC) { DEBUG(dbgs() << " NOT Inlining: cost=" << IC.getCost() << ", thres=" << (IC.getCostDelta() + IC.getCost()) << ", Call: " << *CS.getInstruction() << "\n"); return false; } Code after instrumentalization: bool doInlinging = (bool)IC; DecisionTreeProxy *dec...
2017 Sep 17
2
RFC: Use closures to delay construction of optimization remarks
...lt;< NV("Callee", Callee) << " not inlined into " > Transforms/IPO/Inliner.cpp- << NV("Caller", Caller) << " because too costly to inline (cost=" > Transforms/IPO/Inliner.cpp- << NV("Cost", IC.getCost()) > Transforms/IPO/Inliner.cpp- << ", threshold=" << NV("Threshold", IC.getThreshold()) << ")"); > > Then inside ORE we return right away if the remarks for the given pass is not enabled. > > This is nice and concise howe...
2013 Dec 18
4
[LLVMdev] [RFC] Iterrative compilation framework for Clang/LLVM
...tions (as compiler would do without this framework) > > or to > > follow alternative paths. > > > > Let us consider Inliner example: > > > > Original code: > > > > if (!IC) { > > DEBUG(dbgs() << " NOT Inlining: cost=" << IC.getCost() > > << ", thres=" << (IC.getCostDelta() + IC.getCost()) > > << ", Call: " << *CS.getInstruction() << "\n"); > > return false; > > } > > > > Code after instrumentalization: > > > > bool doIn...
2013 Dec 17
0
[LLVMdev] [RFC] Iterrative compilation framework for Clang/LLVM
...de > whether to > execute default actions (as compiler would do without this framework) > or to > follow alternative paths. > > Let us consider Inliner example: > > Original code: > > if (!IC) { > DEBUG(dbgs() << " NOT Inlining: cost=" << IC.getCost() > << ", thres=" << (IC.getCostDelta() + IC.getCost()) > << ", Call: " << *CS.getInstruction() << "\n"); > return false; > } > > Code after instrumentalization: > > bool doInlinging = (bool)IC; > DecisionTreeP...
2018 Dec 20
2
RegBankSelect complex value mappings
Hi, I’m looking at RegBankSelect’s partially implemented support for deciding to split a value between multiple registers and I’m wondering if it’s actually intended to solve the problem I’m trying to use it for. RegisterBankInfo.h has this example mapping table: /// E.g., /// Let say we have a 32-bit add and a <2 x 32-bit> vadd. We /// can expand the /// <2 x 32-bit> add into
2017 Sep 19
0
RFC: Use closures to delay construction of optimization remarks
...NV("Callee", Callee) << " not inlined into " >> Transforms/IPO/Inliner.cpp- << NV("Caller", Caller) << " because too costly to inline (cost=" >> Transforms/IPO/Inliner.cpp- << NV("Cost", IC.getCost()) >> Transforms/IPO/Inliner.cpp- << ", threshold=" << NV("Threshold", IC.getThreshold()) << ")"); >> >> Then inside ORE we return right away if the remarks for the given pass is not enabled. >> >> This is n...
2013 Dec 19
0
[LLVMdev] [RFC] Iterrative compilation framework for Clang/LLVM
...ework) > > > or to > > > follow alternative paths. > > > > > > Let us consider Inliner example: > > > > > > Original code: > > > > > > if (!IC) { > > > DEBUG(dbgs() << " NOT Inlining: cost=" << IC.getCost() > > > << ", thres=" << (IC.getCostDelta() + IC.getCost()) > > > << ", Call: " << *CS.getInstruction() << "\n"); > > > return false; > > > } > > > > > > Code after instrumentalization:...
2010 Jan 31
2
[LLVMdev] Crash in PBQP register allocator
...(cost = 0.000000e+00) Selected 1 for node 2 (cost = 0.000000e+00) Selected 1 for node 1 (cost = 0.000000e+00) llc: /home/lhames/Projects/llvm/llvm-broken-pbqp/llvm/lib/CodeGen/RegAllocPBQP.cpp:701: bool<unnamed>::PBQPRegAlloc::mapPBQPToRegAlloc(const PBQP::Solution&): Assertion `solution.getCost() != std::numeric_limits<PBQP::PBQPNum>::infinity() && "Invalid (infinite cost) solution for PBQP problem."' failed. The problem is that node 5 is being allocated an infinite cost option (which implies that all its options have infinite cost). The following steps lead t...
2010 Feb 01
0
[LLVMdev] Crash in PBQP register allocator
...t; Selected 1 for node 2 (cost = 0.000000e+00) > Selected 1 for node 1 (cost = 0.000000e+00) > llc: /home/lhames/Projects/llvm/llvm-broken-pbqp/llvm/lib/CodeGen/RegAllocPBQP.cpp:701: > bool<unnamed>::PBQPRegAlloc::mapPBQPToRegAlloc(const PBQP::Solution&): > Assertion `solution.getCost() != > std::numeric_limits<PBQP::PBQPNum>::infinity() && "Invalid (infinite > cost) solution for PBQP problem."' failed. > > The problem is that node 5 is being allocated an infinite cost option > (which implies that all its options have infinite cost). T...
2010 Jan 28
0
[LLVMdev] Crash in PBQP register allocator
Hi Lang, I'm surprised about the fact that you omit R1/R2 reductions in some cases. Can you give a more detailed description of the bug (e.g. a PBQP dump)? Best regards, Sebastian Lang Hames wrote: > Hi Sachin, llvm-dev, > > I've just committed a new PBQP solver which, among other things, > should take care of this bug. > > Please let me know how it works out for you.
2010 Jan 26
3
[LLVMdev] Crash in PBQP register allocator
Hi Sachin, llvm-dev, I've just committed a new PBQP solver which, among other things, should take care of this bug. Please let me know how it works out for you. Cheers, Lang. On Tue, Dec 15, 2009 at 5:54 PM, Lang Hames <lhames at gmail.com> wrote: > Hi Sachin, > > Yes. Bernhard Scholz and I have just discussed a fix for this. I hope to > commit it in the next few days. I