Add SPV_NV_cooperative_matrix2 and SPV_NV_tensor_addressing

[jeffbolznv]

No description provided.

[Naghasan]

I think only the quantifier suggestions are truly out of sync with the text, the rest is more nitpicking

[Naghasan]

According to extension text

Suggested change

	{ "kind" : "MemoryAccess", "name" : "'Memory Operand'"},
	{ "kind" : "TensorAddressingOperands", "name" : "'Tensor Addressing Operands'"}
	{ "kind" : "MemoryAccess", "name" : "'Memory Operand'", "quantifier" : "?"},
	{ "kind" : "TensorAddressingOperands", "name" : "'Tensor Addressing Operands'", "quantifier" : "?"}

[jeffbolznv]

I'm not clear on the effect of this quantifier change. The MemoryAccess and TensorAddressingOperands masks are required, but additional literal values are optional and depend on those flags. So I think this should not be considered optional? I'm also not sure it actually has any effect in jsonToSpirv.cpp based on the "kind".

[Naghasan]

Oh right, other ops make the absence of MemoryAccess equivalent to setting None (and that's modelled this way) and in the extension OpCooperativeMatrixLoadTensorNV and OpCooperativeMatrixStoreTensorNV have 6+ and 4+ words respectively, so I made assumption they could also be omitted (I was actually going to make a comment about the wording on these operands). So the extension should probably says 8+ and 6+ then.

[jeffbolznv]

Agreed, I will make that change.

[Naghasan]

Suggested change

	{ "kind" : "MemoryAccess", "name" : "'Memory Operand'"},
	{ "kind" : "TensorAddressingOperands", "name" : "'Tensor Addressing Operands'"}
	{ "kind" : "MemoryAccess", "name" : "'Memory Operand'", "quantifier" : "?"},
	{ "kind" : "TensorAddressingOperands", "name" : "'Tensor Addressing Operands'", "quantifier" : "?"}

[bashbaug]

Merging as discussed in the October 23rd teleconference.