Also fix the issue of multiple -m[no-]wavefrontsize64 options to make the last one wins.
Details
Diff Detail
Event Timeline
clang/test/Driver/amdgpu-macros.cl | ||
---|---|---|
380–381 | Can you also check with the flags reversed, -mno-wavefrontsize64 -mwavefrontsize64 |
clang/lib/Driver/ToolChains/AMDGPU.cpp | ||
---|---|---|
396–397 | Why isn't this using hasFlag? DriverArgs.hasFlag(options::OPT_fcuda_flush_denormals_to_zero, options::OPT_fno_cuda_flush_denormals_to_zero, getDefaultDenormsAreZeroForTarget(Kind))) |
clang/lib/Driver/ToolChains/AMDGPU.cpp | ||
---|---|---|
396–397 | hasFlag always return true or false, but here we have 3 cases : no arg, last arg is wave64, last arg is no-wave64. |
clang/lib/Driver/ToolChains/AMDGPU.cpp | ||
---|---|---|
396–397 | hasFlag considers all of these. The features only really need to add +wavefrontsze64 or not based on true or false, the rest is just noise |
clang/lib/Driver/ToolChains/AMDGPU.cpp | ||
---|---|---|
396–397 | I have a simpler solution. will update |
Why is this not redundant with the features check?