Weird update_llc_test_checks behavior?

I've run update_llc_test_checks on a set of tests and am seeing some
weird behavior. The CHECK lines appear directly after the function's
first line, even if there are multiple arguments. E.g.:

define <vscale x 4 x i32> @sel_nxv4i32(<vscale x 4 x i1> %p,
; CHECK-LABEL: sel_nxv4i32:
; CHECK: // %bb.0:
; CHECK-NEXT: mov z0.s, p0/m, z1.s
; CHECK-NEXT: ret
                                       <vscale x 4 x i32> %dst,
                                       <vscale x 4 x i32> %a) {

Is that the intended behavior? Or am I doing something wrong?

Thanks,
Cam

I've seen that, it doesn't actually add the check-lines after the `{`,
but after the end of the line where the function name matched.
So the fix is to make sure that function definition,
including starting `{`, is a single line.

Roman.

I would first try to not (manually) split the function definition across multiple lines. The update scripts are simple beasts.

Thanks, Roman. I guess I've never had a declaration span multiple
lines before. :confused: