search for: i_landingpad

Displaying 4 results from an estimated 4 matches for "i_landingpad".

2012 Jan 11
3
[LLVMdev] landingpad instruction documentation is vague
On Wed, Jan 11, 2012 at 11:37:50AM +0100, Duncan Sands wrote: > Hi Yuri, > > > 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? > > if it doesn't match...
2012 Jan 10
3
[LLVMdev] landingpad instruction documentation is vague
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 "result_type" i...
2012 Jan 11
0
[LLVMdev] landingpad instruction documentation is vague
Hi Yuri, > 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? if it doesn't match a clause then the exception continu...
2012 Jan 11
0
[LLVMdev] landingpad instruction documentation is vague
On Jan 11, 2012, at 3:15 AM, 陳韋任 wrote: > On Wed, Jan 11, 2012 at 11:37:50AM +0100, Duncan Sands wrote: >> Hi Yuri, >> >>> 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? >> >>...