search for: ty_2

Hi Chris, >>> Is it intended that "cleanup ty_1, ty_2" potentially be different to >>> "cleanup ty_1 cleanup ty_2"? Perhaps this is useful for funky personality >>> functions. >>> >> Yeah. One can basically interleave the catches and filters. But having two catch or two filter clauses in a row should be...

On Aug 2, 2011, at 10:28 AM, Duncan Sands wrote: >>>> Is it intended that "cleanup ty_1, ty_2" potentially be different to >>>> "cleanup ty_1 cleanup ty_2"? Perhaps this is useful for funky personality >>>> functions. >>>> >>> Yeah. One can basically interleave the catches and filters. But having two catch or two filter clauses i...

...lvm.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 &q...

...;>> >>> // 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. >> >>...

...9;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. Is it intended that "cleanup ty_1, ty_2&quo...

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

...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...

...39;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 instructions in a given function. A landingpad instruction must contain at least one cleanup, catc...

...'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 conta...