Add more haddocks for AST Instructions

[kquick]

No description provided.

[RyanGlScott]

This part of the sentence is worded confusingly, as it describes "the third" twice in a row, but with different descriptions. Perhaps just shorten this to "the third argument is the mask".

[kquick]

Oops, yes, the second line is leftover garbage.

[RyanGlScott]

This goes through the effort of naming the input vectors V1 and V2, but it then never uses the names V1 or V2 in the rest of the Haddocks. Perhaps shorten this to "the first and second arguments are the input vectors, and the third argument is the mask".

[RyanGlScott]

There is some rather unusual capitalization going on here, between:

• "FunctionType" (is that supposed to be code?)
• "The Function target" (why is Function randomly capitalized?)
• "onSuccess"/"onException" (why do these randomly use lowerCamelCase?)

I thought that perhaps these might have been taken from the LLVM Language Reference Manual entry for invoke, but I don't see anything of the sort there, so I'm not sure where these conventions came from.

[RyanGlScott]

Minor formatting nit picks:

Suggested change

	-- ^ Accesses arguments passed through "varargs" areas of a function call.
	-- The argument is a va_list*; this instruction returns the value of the
	-- specified type located at the target and increments the pointer.
	-- ^ Accesses arguments passed through \"varargs\" areas of a function call.
	-- The argument is a @va_list*@; this instruction returns the value of the
	-- specified type located at the target and increments the pointer.

[RyanGlScott]

Part of this sentence is redundant. Perhaps:

Suggested change

	(key values are unique). If the value is not found in the table,
	the second argument is the default destination if the target is
	not in the table.
	(key values are unique). The second argument is the default
	destination if the target is not in the table.

[RyanGlScott]

Minor formatting nit picks:

Suggested change

	{- ^ Target of an exception (from the Invoke instruction).
	* Arguments:
	1. The result type (the values set by the personality function
	on re-entry to the function).
	2. the second argument may be the personality function, which defines
	values on re-entry. This is used in older LLVM versions and is
	not supplied for recent LLVM versions.
	3. True if this block is a "cleanup"
	4. The list of clauses to handle the exception; The clauses are
	used to match the exception thrown.
	* If no clause matches and cleanup not set, continue unwinding up
	the stack (see Resume).
	{- ^ Target of an exception (from the 'Invoke' instruction).
	* Arguments:
	1. The result type (the values set by the personality function
	on re-entry to the function).
	2. the second argument may be the personality function, which defines
	values on re-entry. This is used in older LLVM versions and is
	not supplied for recent LLVM versions.
	3. True if this block is a "cleanup"
	4. The list of clauses to handle the exception; The clauses are
	used to match the exception thrown.
	* If no clause matches and cleanup not set, continue unwinding up
	the stack (see 'Resume').

[RyanGlScott]

Minor formatting nit pick:

Suggested change

	interrupted by a LandingPad instruction.
	interrupted by a 'LandingPad' instruction.

[RyanGlScott]

For consistency:

Suggested change

	{- ^ * Used to stop propagation of @undef@ and @poison@ values.
	* If the argument is undef or poison, returns an arbitrary (but fixed)
	value of that type instead, otherwise a no-op and returns its
	argument.
	{- ^ * Used to stop propagation of @undef@ and @poison@ values.
	* If the argument is @undef@ or @poison@, returns an arbitrary (but fixed)
	value of that type instead, otherwise a no-op and returns its
	argument.

[kquick]

Sorry about the bad syntax: I was making these changes as a side-effect of some other work and decided it would be better to commit them than discard them, but I did the former without proofreading and converting in-progress to final product. Hopefully these look better now.