search for: ty_n

...e second does. yes there is something about the order :) When front-ends output code, all catches come before filters, but after inlining you can get: catches, filters, catches, filters etc and this ordering needs to be preserved. Also, filters are different from catches: filter ty_1, ty_2, ..., ty_N matches any exception that would not be caught by any of ty_1, ty_2, ..., ty_N. This is quite different to filter ty_1, filter ty_2, ..., filter ty_N. For example, suppose you throw ty_2. Then the filter ty_1, ty_2, ..., ty_N wouldn't match that, but filter ty_1 would. So filter ty_1, ...,...

...yes there is something about the order :) When front-ends output code, all > catches come before filters, but after inlining you can get: catches, filters, > catches, filters etc and this ordering needs to be preserved. Also, filters > are different from catches: filter ty_1, ty_2, ..., ty_N matches any exception > that would not be caught by any of ty_1, ty_2, ..., ty_N. This is quite > different to filter ty_1, filter ty_2, ..., filter ty_N. For example, suppose > you throw ty_2. Then the filter ty_1, ty_2, ..., ty_N wouldn't match that, > but filter ty_1 would. &g...

...;> // 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 instructions in a given function. >> >> Is it intended th...

...hen front-ends output >> code, all >> catches come before filters, but after inlining you can get: >> catches, filters, >> catches, filters etc and this ordering needs to be preserved. >> Also, filters >> are different from catches: filter ty_1, ty_2, ..., ty_N matches >> any exception >> that would not be caught by any of ty_1, ty_2, ..., ty_N. This is >> quite >> different to filter ty_1, filter ty_2, ..., filter ty_N. For >> example, suppose >> you throw ty_2. Then the filter ty_1, ty_2, ..., ty_N wouldn'...

...9; 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 instructions in a given function. > > Is it intended that "cleanup ty_1,...

...xception' 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. -Eli

...n' 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 instructions in a given function. Is it intended that "cleanup ty_1, ty_2" potentially be...

...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 instructions in a given function. A landingpad instruction must contain at least one cleanup, catch, or filter clause...

...tion' 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 instructions in a given function. > > A landingpad instruction must contain at least one cle...