[AMDGPU][NFC] Remove autogenerated comment for test

[vangthao]

Summary

D112733 added a non-generated test so the comment is now misleading.

[foad]

Actually I'd much prefer that the test still *was* autogenerated, otherwise it gets much harder to update the checks. I've run into this a few times with patches I've been working on in the last couple of weeks. Is there a good reason why the test you added in D112733 had to be non-auto-generated? Could it be split into a different file?

[foad]

Not surprisingly someone has now re-auto-generated the checks in this file thus clobbering your hand written checks for cvt_f32_ubyte0_vector - see D114777.

[vangthao]

My original intention with this test was to showcase exactly which instructions we care about but I do see the issue now in updating this test. I can remove the GFX9 check and auto-generate the test again. Will that be fine?

[foad]

In D112839#3170303, @vangthao wrote:

My original intention with this test was to showcase exactly which instructions we care about but I do see the issue now in updating this test. I can remove the GFX9 check and auto-generate the test again. Will that be fine?

Sure, but I don't think there's any need to do anything at all - now that we are testing GFX9, why not keep it?

[vangthao]

Sounds good to me.

llvm/test/CodeGen/AMDGPU/cvt_f32_ubyte.ll

-; NOTE: Assertions have been autogenerated by utils/update_llc_test_checks.py
 ; RUN: llc -mtriple=amdgcn-- -mcpu=tahiti -verify-machineinstrs < %s | FileCheck %s -check-prefixes=GCN,SI
 ; RUN: llc -mtriple=amdgcn-- -mcpu=tonga -mattr=-flat-for-global -verify-machineinstrs < %s | FileCheck %s -check-prefixes=GCN,VI
 ; RUN: llc -mtriple=amdgcn-- -mcpu=gfx1010 -verify-machineinstrs < %s | FileCheck %s -check-prefixes=GFX10
 ; RUN: llc -mtriple=amdgcn-- -mcpu=gfx908 -start-before=amdgpu-isel -verify-machineinstrs < %s | FileCheck %s -check-prefixes=GFX9
 
 declare i32 @llvm.amdgcn.workitem.id.x() nounwind readnone
 declare i32 @llvm.amdgcn.workitem.id.y() nounwind readnone