Displaying 7 results from an estimated 7 matches for "hexagonhardwareloops".
2014 Jul 14
2
[LLVMdev] Register Machine Pass
Where is the documentation about registering a machine pass? I'm unable to
find it.
I have built a machine function pass similar to the one found in
HexagonHardwareLoops.cpp. So I have generated a machine pass.cpp file,
modified 'Target'.h and 'Target'TargetMachine.cpp (to add pass via
addPass() in the addPreRegAlloc()). All this builds/compiles fine.
When running llc the pass does not get executed.
I seem to be missing some steps? Potentially reg...
2014 Jul 14
3
[LLVMdev] Register Machine Pass
...i at nvidia.com>
wrote:
> On Mon, 2014-07-14 at 08:31 -0700, Ryan Taylor wrote:
> > Where is the documentation about registering a machine pass? I'm
> > unable to find it.
> >
> >
> > I have built a machine function pass similar to the one found in
> > HexagonHardwareLoops.cpp. So I have generated a machine pass.cpp file,
> > modified 'Target'.h and 'Target'TargetMachine.cpp (to add pass via
> > addPass() in the addPreRegAlloc()). All this builds/compiles fine.
> >
> >
> > When running llc the pass does not get executed....
2011 Dec 16
2
[LLVMdev] Update CMakeLists.txt for Target Hexagon to adjust MCTargetDesc path for HexagonMCAsmInfo.cpp
...subtarget)
tablegen(LLVM HexagonGenIntrinsics.inc -gen-tgt-intrinsic)
add_public_tablegen_target(HexagonCommonTableGen)
add_llvm_target(HexagonCodeGen
HexagonAsmPrinter.cpp
HexagonCallingConvLower.cpp
HexagonCFGOptimizer.cpp
HexagonExpandPredSpillCode.cpp
HexagonFrameLowering.cpp
HexagonHardwareLoops.cpp
HexagonInstrInfo.cpp
HexagonISelDAGToDAG.cpp
HexagonISelLowering.cpp
*MCTargetDesc/*HexagonMCAsmInfo.cpp
HexagonOptimizeSZExtends.cpp
HexagonRegisterInfo.cpp
HexagonRemoveSZExtArgs.cpp
HexagonSelectionDAGInfo.cpp
HexagonSplitTFRCondSets.cpp
HexagonSubtarget.cpp
Hex...
2011 Dec 16
0
[LLVMdev] Update CMakeLists.txt for Target Hexagon to adjust MCTargetDesc path for HexagonMCAsmInfo.cpp
...rinsics.inc -gen-tgt-intrinsic)
> add_public_tablegen_target(HexagonCommonTableGen)
>
> add_llvm_target(HexagonCodeGen
> HexagonAsmPrinter.cpp
> HexagonCallingConvLower.cpp
> HexagonCFGOptimizer.cpp
> HexagonExpandPredSpillCode.cpp
> HexagonFrameLowering.cpp
> HexagonHardwareLoops.cpp
> HexagonInstrInfo.cpp
> HexagonISelDAGToDAG.cpp
> HexagonISelLowering.cpp
> *MCTargetDesc/*HexagonMCAsmInfo.cpp
> HexagonOptimizeSZExtends.cpp
> HexagonRegisterInfo.cpp
> HexagonRemoveSZExtArgs.cpp
> HexagonSelectionDAGInfo.cpp
> HexagonSplitTFRCondSe...
2015 Nov 17
2
Confused on how to do a machinefunction pass
...difference between
writing machinefunction passes in x86 and other targets?
Thank you,
Fami
On Fri, Nov 6, 2015 at 10:56 AM, fateme Hoseini <hoseini.f at gmail.com> wrote:
> Hi
> So I m trying to write my first backend pass. I created a file in
> target\x86\wawanalyzer.cpp based on hexagonHardwareLoops.cpp file. Now it's
> just a simple file that prints hello to the output. I have attached the
> file to this post.
>
> Then I did the following:
>
> 1. add "FunctionPass *createwawAnalyzer();" line to x86.h
> 2. add file name to CMakelist.txt.
> 3. This is going...
2015 Nov 17
2
Confused on how to do a machinefunction pass
...on passes in x86 and other targets?
> Thank you,
> Fami
>
> On Fri, Nov 6, 2015 at 10:56 AM, fateme Hoseini <hoseini.f at gmail.com>
> wrote:
>
>> Hi
>> So I m trying to write my first backend pass. I created a file in
>> target\x86\wawanalyzer.cpp based on hexagonHardwareLoops.cpp file. Now it's
>> just a simple file that prints hello to the output. I have attached the
>> file to this post.
>>
>> Then I did the following:
>>
>> 1. add "FunctionPass *createwawAnalyzer();" line to x86.h
>> 2. add file name to CMakelis...
2015 Nov 04
3
Confused on how to do a machinefunction pass
Thank you so much.
That helped alot.
Fami
On Wed, Nov 4, 2015 at 9:40 AM, John Criswell <jtcriswel at gmail.com> wrote:
> On 11/3/15 7:54 PM, fateme Hoseini wrote:
>
> Dear John,
> Thank you so much for your help. I looked at those documents. Could you
> kindly answer the following questions:
>
> Does it mean that I have to make my own backend target in order to write