search for: typeandvalu

...tch ty_1, ..., ty_N > makes sense. Agreed. Other notes: a zero-type filter is meaningful (and pretty common — it's the result of 'throw()'), but the ordering of the cleanup bit is not, so I would suggest this grammar: Instruction ::= 'landingpad' Type 'personality' TypeAndValue 'cleanup'? LandingPadClause* LandingPadClause ::= 'catch' TypeAndValue LandingPadClause ::= 'filter' TypeAndValue* John.

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 semantically the same as the

...e. > > Agreed. Other notes: a zero-type filter is meaningful (and pretty > common ? it's the result of 'throw()'), but the ordering of the > cleanup > bit is not, so I would suggest this grammar: > > Instruction ::= 'landingpad' Type 'personality' TypeAndValue > 'cleanup'? LandingPadClause* > LandingPadClause ::= 'catch' TypeAndValue > LandingPadClause ::= 'filter' TypeAndValue* > > John. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/...

...rn false; } - /// ParseOptionalStackAlignment /// ::= /* empty */ /// ::= 'alignstack' '(' 4 ')' @@ -4198,11 +4206,12 @@ int LLParser::ParseStore(Instruction *&Inst, PerFunctionState &PFS) { /// ParseCmpXchg /// ::= 'cmpxchg' 'volatile'? TypeAndValue ',' TypeAndValue ',' TypeAndValue -/// 'singlethread'? AtomicOrdering +/// 'singlethread'? AtomicOrdering AtomicOrdering int LLParser::ParseCmpXchg(Instruction *&Inst, PerFunctionState &PFS) { Value *Ptr, *Cmp, *New; LocTy PtrLoc, CmpLoc, New...