search for: resultval

....getNode()) { Tmp3 = LegalizeOp(Tmp1); Tmp4 = LegalizeOp(Tmp1.getValue(1)); <----------------- what is the value expected } What is the value supposed to legalized by the second call to legalizeOp. ? My problem is that the second call asserts inside legalize ops at ResultVals[Op.getResNo()]; b'cos ResultVals has only 1 element and Op.resno is 0. I am not sure if I provided enough context. Please let me know if more information is needed. thanks shrey

> My problem is that the second call asserts inside legalize ops at > ResultVals[Op.getResNo()]; b'cos ResultVals has only 1 element and > Op.resno is 0. Looks like you lowered the load improperly. It should return 2 values: the value loaded and a chain. -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

...oad->getOperand(1), load->getBasePtr(), des }; DAG.getNode(CustomOpc, NodeTys, Ops, 4); thanks again! shrey On Thu, Nov 12, 2009 at 4:41 PM, Anton Korobeynikov <anton at korobeynikov.info> wrote: >> My problem is that the second call asserts inside legalize ops at >> ResultVals[Op.getResNo()]; b'cos ResultVals has only 1 element and >> Op.resno is 0. > Looks like you lowered the load improperly. It should return 2 values: > the value loaded and a chain. > > -- > With best regards, Anton Korobeynikov > Faculty of Mathematics and Mechanics, Sain...

...need a way to link the landing pads from the parent function to the outlined handlers. I propose doing this by extending the syntax of the landing pad instruction to allow the address of an outlined handler to be attached to catch and cleanup clauses. The current syntax for landingpad is: <resultval> = landingpad <resultty> personality <type> <pers_fn> <clause>+ <resultval> = landingpad <resultty> personality <type> <pers_fn> cleanup <clause>* <clause> := catch <type> <value> <clause> := filter <array co...

...head bias; adjusted = values adjusted for look-ahead bias.) 1) I could a) do calculations on unadjusted values then b) adjust the resulting values for look-ahead bias. Here is what I mean: a) I could say the following using time series of val1: [(val1 - val1 4 periods ago) / val1 4 periods ago] = resultval. ("Periods" correspond to the z.dates in my example below.) b) Then I would adjust the resultval for look-ahead based on val1's associated report date. Note: I don't think this will be the fastest. 2) I could do the same calculation [(val1 - val1 4 periods ago) / val1 4 periods a...

...lues adjusted for look-ahead bias.) > > 1) I could a) do calculations on unadjusted values then b) adjust the > resulting values for look-ahead bias. Here is what I mean: > a) I could say the following using time series of val1: [(val1 - val1 4 > periods ago) / val1 4 periods ago] = resultval. ("Periods" correspond to > the z.dates in my example below.) > b) Then I would adjust the resultval for look-ahead based on val1's > associated report date. > Note: I don't think this will be the fastest. > > 2) I could do the same calculation [(val1 - val1 4 pe...

...need a way to link the landing pads from the parent function to the outlined handlers. I propose doing this by extending the syntax of the landing pad instruction to allow the address of an outlined handler to be attached to catch and cleanup clauses. The current syntax for landingpad is: <resultval> = landingpad <resultty> personality <type> <pers_fn> <clause>+ <resultval> = landingpad <resultty> personality <type> <pers_fn> cleanup <clause>* <clause> := catch <type> <value> <clause> := filter <array co...

> On Jan 23, 2017, at 12:36, Friedman, Eli via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On 1/23/2017 5:21 AM, Jonas Paulsson wrote: >> Hi Eli, >> >> I would like to clarify generally what the difference is between returning SDValue() and Op (input argument unchanged) from LowerOperation()? >> >> My understanding is that returning SDValue()

...nly support Dwarf exception handling and setjmp/longjmp exception handling which both use { i8*, i32 }, so while you can use any type in the IR, only this type will work if you use the LLVM code generators to produce code for your machine. Note that the language reference explicitly says "The resultval has the type somety". > 3. What are the allowed values and types passed to catch clause? I see > that practically type is i8* and value is bitcast (i8** @<typeinfo> to > i8*). Is this target specific? If yes, documentation should mention > this, if not, it should describe t...

I am new to the landingpad (which is relatively new too). Documentation http://llvm.org/docs/LangRef.html#i_landingpad leaves some questions open: 1. What happens when actual exception type isn't listed in catch or filter clauses? Does it still return the corresponding structure like if it was listed? Or behavior is undefined? 2. What is 'somety'? Shouldn't it maybe say