[llvm-commits] [llvm] r48173 - /llvm/trunk/docs/LangRef.html

Duncan Sands baldrick at free.fr
Mon Mar 10 22:38:00 PDT 2008

Hi Devang,

> +type of each return value must be '<a href="#t_firstclass">first class</a>'

must be -> must be a

> + type.  Notice that a function is not <a href="#wellformed">well formed</a> 

Notice -> Note

> +if there exists a '<tt>ret</tt>' instruction inside of the function that 
> +returns values that does not match the return type of the function.</p>

that does not match -> that do not match

> +return value. If the instruction returns multiple values then these 
> +value can only be accessed through '<a href="#i_getresult"><tt>getresult</tt>

value can -> values can
accessed through -> accessed through a

> +</a>' insctruction.</p>

insctruction -> instruction

> +continued at the dynamically nearest "exception" label. If the callee function 
> +returns multiple values then individual return values are accessed only through

are accessed only through -> are only accessible through a

> +</tt>' instruction returns multiple values then the return value of the

the return value -> the return values

> +function is only accessed through '<tt><a href="#i_getresult">getresult</a>

is only accessed through -> are only accessible through a

> +from multiple values returned by '<tt><a href="#i_call">call</a></tt>'

returned by -> returned by a

> +The '<tt>getresult</tt>' instruction takes return value as first argument. The

takes return value -> takes a return value

> +value must have <a href="#t_struct">structure type</a>. The second argument 
> +is unsigned index value. 

is unsigned -> is an unsigned

> +The '<tt>getresult</tt>' instruction extracts element identified by

extracts element -> extracts the element



More information about the llvm-commits mailing list