nvptx: Enhance '-march-map=[...]' test cases (was: [committed][nvptx] Add march-map)

Hi! On 2022-03-29T14:03:22+0200, Tom de Vries via Gcc-patches wrote: > [...] > > gcc/testsuite/ChangeLog: > > 2022-03-29 Tom de Vries > > PR target/104714 > * gcc.target/nvptx/march-map.c: New test. Pushed to trunk branch commit ee6711ead30876daf2a8a66f8647cad95470fe79 "nvptx: En

Re: [committed][nvptx] Add march-map

Hi Tom! On 2022-03-29T14:03:22+0200, Tom de Vries via Gcc-patches wrote: > Say we have an sm_50 board, and we want to run a benchmark using the highest > possible march setting. > > Currently there's march=sm_30, march=sm_35, march=sm_53, but no march=sm_50. > > So, we'd need to pick march=sm_35

[committed][nvptx] Add march-map

Hi, Say we have an sm_50 board, and we want to run a benchmark using the highest possible march setting. Currently there's march=sm_30, march=sm_35, march=sm_53, but no march=sm_50. So, we'd need to pick march=sm_35. Likewise, for a test script that handles multiple boards, we'd need a mapping