search for: argvalue

...( MP, true ); > > As Reid pointed out, changing true to false will get it to work. as I've posted already, I got Segmentation Fault. Now, i have re-compiled LLVM with debug support. The evaluation is broken at line 78 in file: lib/ExecutionEngine/JIT/JIT.cpp The assertion assert(ArgValues.size() == 1); fails. But what's wrong? My function has type int FooF(void); so ArgValues should have size 0, right? BTW, the code of runFunction is quite unclear, indeed, for some reason cases ArgValues==3 and ArgValues==1 are specially considered... I looked in JIT.h for more description...

...changing true to false will get it to work. > > as I've posted already, I got Segmentation Fault. > Now, i have re-compiled LLVM with debug support. > > The evaluation is broken at line 78 in file: > lib/ExecutionEngine/JIT/JIT.cpp > > The assertion > > assert(ArgValues.size() == 1); > > fails. But what's wrong? My function has type > int FooF(void); > so ArgValues should have size 0, right? Yes, you're right. > BTW, the code of runFunction is quite unclear, indeed, for some reason > cases ArgValues==3 and ArgValues==1 are specially co...

On Sat, 14 Aug 2004, Valery A.Khamenya wrote: > hm, here is the part of my code starting LLVM function: > > /////////////////////////// > ExistingModuleProvider* MP = new ExistingModuleProvider(M); > ExecutionEngine* EE = ExecutionEngine::create( MP, true ); As Reid pointed out, changing true to false will get it to work. > // Call the `foo' function with no

> If it's that slow, you're probably getting the interpreter instead of the > JIT. Try adding -print-machineinstr to the command line, or -debug, and > see what happens. If you're not getting the JIT, try stepping through the > LLVM program to see where it makes the execution engine and decides which > one to use... (thanks for quick reply) hm, here is the part of my

...abilities, set_arg_capabilities }, + { ARG_EVB_VSIS, get_arg_vsis, set_arg_vsis }, + { ARG_EVB_RTE, get_arg_rte, set_arg_rte }, + { ARG_TLVTXENABLE, get_arg_tlvtxenable, set_arg_tlvtxenable }, + { NULL } +}; + +static int get_arg_tlvtxenable(struct cmd *cmd, char *arg, char *argvalue, + char *obuf) +{ + int value; + char *s; + char arg_path[EVB_BUF_SIZE]; + + if (cmd->cmd != cmd_gettlv) + return cmd_invalid; + + switch (cmd->tlvid) { + case (LLDP_MOD_EVB << 8) | LLDP_EVB_SUBTYPE: +...

...abilities, set_arg_capabilities }, + { ARG_EVB_VSIS, get_arg_vsis, set_arg_vsis }, + { ARG_EVB_RTE, get_arg_rte, set_arg_rte }, + { ARG_TLVTXENABLE, get_arg_tlvtxenable, set_arg_tlvtxenable }, + { NULL } +}; + +static int get_arg_tlvtxenable(struct cmd *cmd, char *arg, char *argvalue, + char *obuf) +{ + int value; + char *s; + char arg_path[EVB_BUF_SIZE]; + + if (cmd->cmd != cmd_gettlv) + return cmd_invalid; + + switch (cmd->tlvid) { + case (LLDP_MOD_EVB << 8) | LLDP_EVB_SUBTYPE: +...

.../ binary? 2. Is there a way, with the existing infrastructure, to do adaptive compilation using the JIT interpreter? Watching said interpreter through GDB shows that it starts off with runFunction() called on the function representing "main", and ends up at the line: rv.IntVal = PF(ArgValues[0].IntVal, (char **)GVTOP(ArgValues[1])); where PF is a pointer to (I think) the machine code representation of main(). So, main() is invoked, and the result returned to the caller. Now, what I'm looking at implementing is something like the following scenario. a. The JIT interpreter start...

On Sep 28, 2007, at 11:36 AM, <Alireza.Moshtaghi at microchip.com> <Alireza.Moshtaghi at microchip.com> wrote: > I moved my code to 2.1 but still the same. > If I make ADD i16 legal, then it goes through, but it has problem > expanding it to i8. > Should I go ahead and customize it and do the same for all > instructions? > Or there is a more general thing that I

I moved my code to 2.1 but still the same. If I make ADD i16 legal, then it goes through, but it has problem expanding it to i8. Should I go ahead and customize it and do the same for all instructions? Or there is a more general thing that I can do? A. -----Original Message----- From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Chris Lattner Sent:

Hi, This set of patches contains the initial implementation of the IEEE 802.1Qbg standard: code for the exchange of EVB TLVs in LLDP frames to negotiate VSI capabalities as well as VDP VSI TLVs between a host with virtual machines and an adjacent switch. It supports setting the parameters of the TLV exchange from the command line using lldptool. VDP profiles consisting of

Hi, This set of patches contains the initial implementation of the IEEE 802.1Qbg standard: code for the exchange of EVB TLVs in LLDP frames to negotiate VSI capabalities as well as VDP VSI TLVs between a host with virtual machines and an adjacent switch. It supports setting the parameters of the TLV exchange from the command line using lldptool. VDP profiles consisting of

...9;m not sure if I may be breaking something in there. Here is my code in the formalizing arguments (copied ISD::MERGE_VALUES from PowerPC implementation, not sure if it is really needed) static SDOperand LowerFORMAL_ARGUMENTS(SDOperand Op, SelectionDAG &DAG){ SmallVector<SDOperand, 8> ArgValues; SDOperand Root = Op.getOperand(0); // Return the new list of results. std::vector<MVT::ValueType> RetVT(Op.Val->value_begin(), Op.Val->value_end()); const Function* Fn = DAG.getMachineFunction().getFunction(); std::cout<<Op.Val->g...

...orrupt stack?) ---------------------- However, if the program doesn't do anything (i.e., an empty main() function). The lli won't crash. I traced lli using gdb, and found that it crashes within JIT::runFunction(). In particular, the problem is in line 70 of JIT.cpp: int ExitCode = PF(ArgValues[0].IntVal, (char **) GVTOP (ArgValues[1]), (const char **) GVTOP (ArgValues[2])); Is anybody having any idea about this? Thanks a lot. Shukang Zhou

On Aug 27, 2010, at 11:53 AMPDT, Yuri wrote: > On 08/27/2010 11:32, Yuri wrote: >> As I understand only one of TCRETURNri64 and RET should be created. >> I have sources of rev.112200. >> >> Here is the stack when TCRETURNri64 instruction is created: >> #1 0x0000000802c8b4e2 in llvm::MachineFunction::CreateMachineInstr >> (this=0x30eb000, TID=@0x803a78940,

Hi, this set of patches contains the initial implementation of the IEEE 802.1Qbg standard: code for the exchange of EVB TLVs in LLDP frames to negotiate VSI capabalities as well as VDP VSI TLVs between a host with virtual machines and an adjacent switch. It supports setting the parameters of the TLV exchange from the command line using lldptool. VDP profiles consisting of

Hi, this set of patches contains the initial implementation of the IEEE 802.1Qbg standard: code for the exchange of EVB TLVs in LLDP frames to negotiate VSI capabalities as well as VDP VSI TLVs between a host with virtual machines and an adjacent switch. It supports setting the parameters of the TLV exchange from the command line using lldptool. VDP profiles consisting of

...false, 0)); } ... [2]: LowerFormalArguments ... if (VA.isRegLoc()) { // Arguments passed in registers. const TargetRegisterClass *RC = ARC::CPURegsRegisterClass; unsigned int Register = MF.addLiveIn(VA.getLocReg(), RC); EVT RegisterValueType = VA.getLocVT(); ArgValue = DAG.getCopyFromReg(Chain, dl, Register, RegisterValueType); InVals.push_back(ArgValue); } else { // Sanity check assert(VA.isMemLoc()); // Load the argument to a virtual register unsigned ObjSize = VA.getLocVT().getSizeInBits()/8; if (ObjSize != 4) {...

...fffffff8b50) at /tmp/llvm-svn/llvm/lib/ExecutionEngine/JIT/JIT.cpp:633 #14 0x0000000802f507e4 in llvm::JIT::getPointerToFunction (this=0x327a7e0, F=0x4530bd0) at /tmp/llvm-svn/llvm/lib/ExecutionEngine/JIT/JIT.cpp:719 #15 0x0000000802f4f194 in llvm::JIT::runFunction (this=0x327a7e0, F=0x4530bd0, ArgValues=@0x7fffffff9230) at /tmp/llvm-svn/llvm/lib/ExecutionEngine/JIT/JIT.cpp:405 #16 0x0000000802f4fe4f in llvm::JIT::runFunction (this=0x327a7e0, F=0x4530c60, ArgValues=@0x7fffffff9350) at /tmp/llvm-svn/llvm/lib/ExecutionEngine/JIT/JIT.cpp:561 TCRETURNri64 creation stack (created second): #1 0x000...

Hi, this set of patches contains the initial implementation of the IEEE 802.1Qbg standard: code for the exchange of EVB TLVs in LLDP frames to negotiate VSI capabalities as well as VDP VSI TLVs between a host with virtual machines and an adjacent switch. It supports setting the parameters of the TLV exchange from the command line using lldptool. VDP profiles consisting of

Hi, this set of patches contains the initial implementation of the IEEE 802.1Qbg standard: code for the exchange of EVB TLVs in LLDP frames to negotiate VSI capabalities as well as VDP VSI TLVs between a host with virtual machines and an adjacent switch. It supports setting the parameters of the TLV exchange from the command line using lldptool. VDP profiles consisting of