Fix comments

Author: arsenm

llvm/lib/Target/AMDGPU/AMDGPU.td

@@ -1238,7 +1238,7 @@ def FeatureSetPrioIncWgInst : SubtargetFeature<"setprio-inc-wg-inst",
 // Subtarget Features (options and debugging)
 //===------------------------------------------------------------===//
 
-// Ugly hack to accomodate an assembling modules with mixed
+// Ugly hack to accomodate assembling modules with mixed
 // wavesizes. Ideally we would have a mapping symbol in assembly which
 // would keep track of which sections of code should be treated as
 // wave32 and wave64. Instead what users do is assemble with both

llvm/lib/Target/AMDGPU/MCTargetDesc/AMDGPUMCTargetDesc.cpp

@@ -97,7 +97,7 @@ createAMDGPUMCSubtargetInfo(const Triple &TT, StringRef CPU, StringRef FS) {
  ? AMDGPU::FeatureWavefrontSize32
  : AMDGPU::FeatureWavefrontSize64);
  } else if (IsWave64 && IsWave32) {
- // The wave size is mutually exclusive. If both somehow end up set, wave64
+ // The wave size is mutually exclusive. If both somehow end up set, wave32
  // wins if supported.
  STI->ToggleFeature(AMDGPU::supportsWave32(*STI)
  ? AMDGPU::FeatureWavefrontSize64

llvm/test/MC/AMDGPU/wavesize-feature-unsupported-target.s

@@ -1,7 +1,7 @@
 // RUN: llvm-mc -triple=amdgcn -mcpu=gfx1250 -mattr=+wavefrontsize64 -o - %s | FileCheck -check-prefix=GFX1250 %s
 // RUN: llvm-mc -triple=amdgcn -mcpu=gfx900 -mattr=+wavefrontsize32 -o - %s | FileCheck -check-prefix=GFX900 %s
 
-// Both are supported, but not at the same time
+// Both sure setting both modes is supported at the same time.
 // RUN: llvm-mc -triple=amdgcn -mcpu=gfx1010 -mattr=+wavefrontsize32,+wavefrontsize64 %s | FileCheck -check-prefixes=GFX10 %s
 
 // Test that there is no assertion when using an explicit