spirv-val reports OpName and OpLine as not same section about spirv-tools HOT 2 CLOSED

See logical module layout in the spec. In particular:

7. These debug instructions, which must be grouped in the following order:

• All OpString, OpSourceExtension, OpSource, and OpSourceContinued, without forward references.
• All OpName and all OpMemberName.
• All OpModuleProcessed instructions.
  ...

9. All type declarations (OpTypeXXX instructions), all constant instructions, and all global variable declarations (all OpVariable instructions whose Storage Class is not Function). This is the preferred location for OpUndef instructions, though they can also appear in function bodies. All operands in all these instructions must be declared before being used. Otherwise, they can be in any order. This section is the first section to allow use of:

• OpLine and OpNoLine debug information.
• Non-semantic instructions with OpExtInst.

So OpLine can't be present until the type declaration section. When the validator sees OpLine it moves forward to that section which is why the error is that OpName is in the wrong section.

from spirv-tools.

ok, it says

These debug instructions

and not

The debug instructions

so this seems fair to me, thanks for clarify, I have not caught that slight difference before

from spirv-tools.