Displaying 5 results from an estimated 5 matches for "buildproblemfor".
2010 Sep 08
3
[LLVMdev] Complex regalloc contraints
...to represent more esoteric constraints in their
architecture just extends this class, calls the base class to handle all the
basic constraints, then performs their own pass over the function to add in
their constraints:
struct MyTargetPBQPProblemBuilder : public PBQPProblemBuilder {
PBQP::Graph* buildProblemFor(MachineFunction *mf) {
PBQP::Graph* g = PBQPProblemBuilder::buildProblemFor(mf);
// Add additional constraints for my architecture here.
return g;
}
}
Any thoughts or comments? I think this should be a very straightforward
extension.
Cheers,
Lang.
On Wed, Sep 8, 2010 at 8:38 A...
2010 Sep 08
0
[LLVMdev] Complex regalloc contraints
...re esoteric constraints in their architecture just extends this class, calls the base class to handle all the basic constraints, then performs their own pass over the function to add in their constraints:
>
> struct MyTargetPBQPProblemBuilder : public PBQPProblemBuilder {
> PBQP::Graph* buildProblemFor(MachineFunction *mf) {
> PBQP::Graph* g = PBQPProblemBuilder::buildProblemFor(mf);
> // Add additional constraints for my architecture here.
> return g;
> }
> }
>
> Any thoughts or comments? I think this should be a very straightforward extension.
If a target re...
2010 Sep 09
1
[LLVMdev] Complex regalloc contraints
...nstraints in their
> architecture just extends this class, calls the base class to handle all the
> basic constraints, then performs their own pass over the function to add in
> their constraints:
>
> struct MyTargetPBQPProblemBuilder : public PBQPProblemBuilder {
> PBQP::Graph* buildProblemFor(MachineFunction *mf) {
> PBQP::Graph* g = PBQPProblemBuilder::buildProblemFor(mf);
> // Add additional constraints for my architecture here.
> return g;
> }
> }
>
> Any thoughts or comments? I think this should be a very straightforward
> extension.
>
>
&...
2010 Sep 07
0
[LLVMdev] Complex regalloc contraints
On Sep 7, 2010, at 3:01 AM, Carlos Sanchez de La Lama wrote:
> The machine I am targeting has some special requirements for some
> operations, say:
>
> ADD or1, ir1, r5
>
> would add ir1 (input reg 1) and r5 and put the result in or1 (output reg
> 1). The point id that input and output regs have to go paired (this
> meaning an addition of ir1 with whatever always goes to
2010 Sep 07
2
[LLVMdev] Complex regalloc contraints
Hi all,
The machine I am targeting has some special requirements for some
operations, say:
ADD or1, ir1, r5
would add ir1 (input reg 1) and r5 and put the result in or1 (output reg
1). The point id that input and output regs have to go paired (this
meaning an addition of ir1 with whatever always goes to or1, or an in
general irX + whatever goes to orX).
AFAIK, InstrInfo.td only allow