search for: superinstruction

...achineInstrBundle, which is essnetially a VLIW-style machine instruction which can store any MI on each "slot". After the scheduling phase has grouped MIs in bundles, it has to call MIB->pack() method, which takes operands from the MIs in the "slots" and transfers them to the superinstruction. From this point on the bundle is a normal machineinstruction which can be processed by other LLVM passes (such as register allocation). The idea was to make a framework on top of which VLIW/ILP scheduling could be studies using LLVM. It is not completely finished, but it is more or less usable an...

Has anyone attempted the port of LLVM to a VLIW architecture? Is there any publication about it? TIA -- Evandro Menezes Austin, TX emenezes at codeaurora.org Qualcomm Innovation Center, Inc is a member of Code Aurora Forum

...hich is essnetially a VLIW-style machine > instruction which can store any MI on each "slot". After the scheduling > phase has grouped MIs in bundles, it has to call MIB->pack() method, > which takes operands from the MIs in the "slots" and transfers them to > the superinstruction. From this point on the bundle is a normal > machineinstruction which can be processed by other LLVM passes (such as > register allocation). > > The idea was to make a framework on top of which VLIW/ILP scheduling > could be studies using LLVM. It is not completely finished, but it...

...is essnetially a VLIW-style machine > instruction which can store any MI on each "slot". After the > scheduling phase has grouped MIs in bundles, it has to call > MIB->pack() method, which takes operands from the MIs in the "slots" > and transfers them to the superinstruction. From this point on the > bundle is a normal machineinstruction which can be processed by other > LLVM passes (such as register allocation). > > The idea was to make a framework on top of which VLIW/ILP scheduling > could be studies using LLVM. It is not completely finished, but...

...a VLIW-style machine >> instruction which can store any MI on each "slot". After the >> scheduling phase has grouped MIs in bundles, it has to call >> MIB->pack() method, which takes operands from the MIs in the "slots" >> and transfers them to the superinstruction. From this point on the >> bundle is a normal machineinstruction which can be processed by other >> LLVM passes (such as register allocation). >> >> The idea was to make a framework on top of which VLIW/ILP scheduling >> could be studies using LLVM. It is not compl...

...a VLIW-style machine >> instruction which can store any MI on each "slot". After the >> scheduling phase has grouped MIs in bundles, it has to call >> MIB->pack() method, which takes operands from the MIs in the "slots" >> and transfers them to the superinstruction. From this point on the >> bundle is a normal machineinstruction which can be processed by other >> LLVM passes (such as register allocation). >> >> The idea was to make a framework on top of which VLIW/ILP scheduling >> could be studies using LLVM. It is not compl...

...hine >>> instruction which can store any MI on each "slot". After the >>> scheduling phase has grouped MIs in bundles, it has to call >>> MIB->pack() method, which takes operands from the MIs in the "slots" >>> and transfers them to the superinstruction. From this point on the >>> bundle is a normal machineinstruction which can be processed by other >>> LLVM passes (such as register allocation). >>> >>> The idea was to make a framework on top of which VLIW/ILP scheduling >>> could be studies using L...

...hine >>> instruction which can store any MI on each "slot". After the >>> scheduling phase has grouped MIs in bundles, it has to call >>> MIB->pack() method, which takes operands from the MIs in the "slots" >>> and transfers them to the superinstruction. From this point on the >>> bundle is a normal machineinstruction which can be processed by other >>> LLVM passes (such as register allocation). >>> >>> The idea was to make a framework on top of which VLIW/ILP scheduling >>> could be studies using L...

...t;> instruction which can store any MI on each "slot". After the >>>> scheduling phase has grouped MIs in bundles, it has to call >>>> MIB->pack() method, which takes operands from the MIs in the "slots" >>>> and transfers them to the superinstruction. From this point on the >>>> bundle is a normal machineinstruction which can be processed by other >>>> LLVM passes (such as register allocation). >>>> >>>> The idea was to make a framework on top of which VLIW/ILP scheduling >>>> coul...

...gt; instruction which can store any MI on each "slot". After the > >>> scheduling phase has grouped MIs in bundles, it has to call > >>> MIB->pack() method, which takes operands from the MIs in the "slots" > >>> and transfers them to the superinstruction. From this point on the > >>> bundle is a normal machineinstruction which can be processed by other > >>> LLVM passes (such as register allocation). > >>> > >>> The idea was to make a framework on top of which VLIW/ILP scheduling > >>>...

...machine >>> instruction which can store any MI on each "slot". After the >>> scheduling phase has grouped MIs in bundles, it has to call >>> MIB->pack() method, which takes operands from the MIs in the "slots" >>> and transfers them to the superinstruction. From this point on the >>> bundle is a normal machineinstruction which can be processed by other >>> LLVM passes (such as register allocation). >>> >>> The idea was to make a framework on top of which VLIW/ILP scheduling >>> could be studies using LLVM....

...gt; instruction which can store any MI on each "slot". After the > >>> scheduling phase has grouped MIs in bundles, it has to call > >>> MIB->pack() method, which takes operands from the MIs in the "slots" > >>> and transfers them to the superinstruction. From this point on the > >>> bundle is a normal machineinstruction which can be processed by other > >>> LLVM passes (such as register allocation). > >>> > >>> The idea was to make a framework on top of which VLIW/ILP scheduling > >>>...

...gt;> instruction which can store any MI on each "slot". After the >>>> scheduling phase has grouped MIs in bundles, it has to call >>>> MIB->pack() method, which takes operands from the MIs in the "slots" >>>> and transfers them to the superinstruction. From this point on the >>>> bundle is a normal machineinstruction which can be processed by >>>> other LLVM passes (such as register allocation). >>>> >>>> The idea was to make a framework on top of which VLIW/ILP >>>> scheduling coul...

...struction which can store any MI on each "slot". After the >>>>> scheduling phase has grouped MIs in bundles, it has to call >>>>> MIB->pack() method, which takes operands from the MIs in the "slots" >>>>> and transfers them to the superinstruction. From this point on the >>>>> bundle is a normal machineinstruction which can be processed by other >>>>> LLVM passes (such as register allocation). >>>>> >>>>> The idea was to make a framework on top of which VLIW/ILP scheduling >>&...

...ruction which can store any MI on each "slot". After the >>>>> scheduling phase has grouped MIs in bundles, it has to call >>>>> MIB->pack() method, which takes operands from the MIs in the "slots" >>>>> and transfers them to the superinstruction. From this point on the >>>>> bundle is a normal machineinstruction which can be processed by >>>>> other LLVM passes (such as register allocation). >>>>> >>>>> The idea was to make a framework on top of which VLIW/ILP >>>>...

...ruction which can store any MI on each "slot". After the >>>>> scheduling phase has grouped MIs in bundles, it has to call >>>>> MIB->pack() method, which takes operands from the MIs in the "slots" >>>>> and transfers them to the superinstruction. From this point on the >>>>> bundle is a normal machineinstruction which can be processed by >>>>> other LLVM passes (such as register allocation). >>>>> >>>>> The idea was to make a framework on top of which VLIW/ILP >>>>...

...hich is essnetially a VLIW-style machine > instruction which can store any MI on each "slot". After the scheduling > phase has grouped MIs in bundles, it has to call MIB->pack() method, > which takes operands from the MIs in the "slots" and transfers them to > the superinstruction. From this point on the bundle is a normal > machineinstruction which can be processed by other LLVM passes (such as > register allocation). > > The idea was to make a framework on top of which VLIW/ILP scheduling > could be studies using LLVM. It is not completely finished, but it i...