agree, it should be i = 0 or i = 1 in the test code (but doesn't matter)
I understand that the 2nd parameter of vget_lane_f32() should be a constant
ubuntu gcc-4.7 crashes, this is hardly 'expected behaviour'
I would expect gcc to report the error (as it does: "error: argument must be a constant") and continue processing (it does NOT: "confused by earlier errors, bailing out")
agree, it should be i = 0 or i = 1 in the test code (but doesn't matter)
I understand that the 2nd parameter of vget_lane_f32() should be a constant
ubuntu gcc-4.7 crashes, this is hardly 'expected behaviour'
I would expect gcc to report the error (as it does: "error: argument must be a constant") and continue processing (it does NOT: "confused by earlier errors, bailing out")