search for: pers_fn

...ined 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 constant type> <array constant> I'd like to change that to:...

...ad' Instruction >> // >> >> The 'landingpad' instruction replaces the current 'llvm.eh.exception' and >> 'llvm.eh.selector' intrinsics. >> >> // Syntax: >> >> %res = landingpad<somety> personality<ty> <pers_fn> <clause>+ >> >> where >> >> <clause> := >> cleanup >> | catch<ty_1>,<ty_2>, ...,<ty_n> >> | filter<ty_1>,<ty_2>, ...,<ty_m> >> >> and the result has the type '<so...

...ll Wendling wrote: >>> The 'landingpad' instruction replaces the current 'llvm.eh.exception' and >>> 'llvm.eh.selector' intrinsics. >>> >>> // Syntax: >>> >>> %res = landingpad<somety> personality<ty> <pers_fn> <clause>+ >>> >>> where >>> >>> <clause> := >>> cleanup >>> | catch<ty_1>,<ty_2>, ...,<ty_n> >>> | filter<ty_1>,<ty_2>, ...,<ty_m> >>> >>> and the...

...---------- > // The 'landingpad' Instruction > // > > The 'landingpad' instruction replaces the current 'llvm.eh.exception' and > 'llvm.eh.selector' intrinsics. > > // Syntax: > >  %res = landingpad <somety> personality <ty> <pers_fn> <clause>+ > > where > >  <clause> := >       cleanup >    |  catch <ty_1>, <ty_2>, ..., <ty_n> >    |  filter <ty_1>, <ty_2>, ..., <ty_m> | terminate ? You have an example referencing it, but it isn't in the grammar. -E...

...catch<ty_1> >>>> | filter<ty_1> > > .. forcing "catch" or "filter" before each entry. If you don't like that, why not make the grammar be something like: > >>>> %res = landingpad<somety> personality<ty> <pers_fn> (catch<ty>+)? (filter<ty>+)? > > Is there anything specific about the ordering of catch or filter clauses that affect semantics? If so, the first alternative seems cleaner. If not, the second does. yes there is something about the order :) When front-ends output code, all...

...gt;>>>> | filter<ty_1> >> >> .. forcing "catch" or "filter" before each entry. If you don't like that, why not make the grammar be something like: >> >>>>> %res = landingpad<somety> personality<ty> <pers_fn> (catch<ty>+)? (filter<ty>+)? >> >> Is there anything specific about the ordering of catch or filter clauses that affect semantics? If so, the first alternative seems cleaner. If not, the second does. > > yes there is something about the order :) When front-en...

...ined 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 constant type> <array constant> I'd like to change that to:...

...function and ABI). //===-------------------------- // The 'landingpad' Instruction // The 'landingpad' instruction replaces the current 'llvm.eh.exception' and 'llvm.eh.selector' intrinsics. // Syntax: %res = landingpad <somety> personality <ty> <pers_fn> <clause>+ where <clause> := cleanup | catch <ty_1>, <ty_2>, ..., <ty_n> | filter <ty_1>, <ty_2>, ..., <ty_m> and the result has the type '<somety>'. The personality functions must be the same for all landingpad...

...-------- > // The 'landingpad' Instruction > // > > The 'landingpad' instruction replaces the current 'llvm.eh.exception' and > 'llvm.eh.selector' intrinsics. > > // Syntax: > > %res = landingpad<somety> personality<ty> <pers_fn> <clause>+ > > where > > <clause> := > cleanup > | catch<ty_1>,<ty_2>, ...,<ty_n> > | filter<ty_1>,<ty_2>, ...,<ty_m> > > and the result has the type '<somety>'. The personality func...

...------- > // The 'landingpad' Instruction > // > > The 'landingpad' instruction replaces the current 'llvm.eh.exception' and > 'llvm.eh.selector' intrinsics. > > // Syntax: > > %res = landingpad <somety> personality <ty> <pers_fn> <clause>+ > > where > > <clause> := > cleanup > | catch <ty_1>, <ty_2>, ..., <ty_n> > | filter <ty_1>, <ty_2>, ..., <ty_m> > > and the result has the type '<somety>'. The personality funct...