search for: i_ret

...case 1: // ret void [skipped] default: { // ret <values> [skipped] Does it imply that a ret instruction may return more than one values? ret uint 1, uint 2, ubyte 3, uint 4 But at most one return value is allowed, according to http://llvm.cs.uiuc.edu/docs/LangRef.html#i_ret Syntax: ret <type> <value> ; Return a value from a non-void function ret void ; Return from void function How to define a function with multiple return values? The code: uint, uint, ubyte, uint %main() { ret uint 1, uint 2, ubyte 3, uint 4 }...

...ble problem when interpreting any >> *.bc from 2.6? > > The 'free' instruction has been removed from LLVM 2.7. Any .bc files using > it will have a 'call @free' inserted in its place. Thanks. Another question is about 'ret'. http://llvm.org/docs/LangRef.html#i_ret gives the syntax: ret <type> <value> ; Return a value from a non-void function ret void ; Return from void function In the case when the return type is not void, it returns a single value. But if I am looking into the code, the Verifier also allows 'multi...

Jianzhou Zhao wrote: > Hi llvm, > > 1) The lib/VMCore/Verifier.cpp in 2.7 implements Verifier::VerifyType, > which is empty in 2.6. I noticed that it does not check all types, > for example, UnionTyID, OpaqueTyID, LabelTyID, MetadataTyID > and etc are ignored in the 'default' branch. Does it mean we dont > need to check them? We do need to check union. I'll add

Hi llvm, 1) The lib/VMCore/Verifier.cpp in 2.7 implements Verifier::VerifyType, which is empty in 2.6. I noticed that it does not check all types, for example, UnionTyID, OpaqueTyID, LabelTyID, MetadataTyID and etc are ignored in the 'default' branch. Does it mean we dont need to check them? Another question is: How much does Verifier.cpp check statically? Can I take it as a type checker