cc: work around -v split between ld and ccld

[trws]

When the cc wrapper gets a -v argument, it currently assumes it's a version check when mode is either ld or unset. That seems right, but it checks the value of mode before ccld is detected. This moves the code down so that -v on gcc in ccld mode gives us the gcc verbose behavior with wrapper args passed rather than adding no wrapper args.

From #42082

[haampie]

Is it true for all compilers?

[trws]

I can’t say that for 100% certain, but the gcc argument set has become a defacto standard. I spot checked icc, xlc, gcc, pgi, and clang and they all use -v for either the same as gcc or in the case of xlc as a “progress” flag. Also the base macro in auto tools to find a version flag tries -V and —version as well, one of which works on all of the above. On January 17, 2024 at 5:18:31 AM PST, Harmen Stoppels ***@***.***> wrote: Is it true for all compilers? — Reply to this email directly, view it on GitHub<https://urldefense.us/v3/__https://github.com/spack/spack/pull/42111*issuecomment-1895795804__;Iw!!G2kpM7uM-TzIFchu!2cz6nRv-MDZHk-X9Ug3t3NvvS82bZv30wMxm_yybtZMypitsAPOCWi3A5ng7XwX4y76ul7r8vna3QHImzFRPs1zODA4$>, or unsubscribe<https://urldefense.us/v3/__https://github.com/notifications/unsubscribe-auth/AAFBFNIGFDOQFBAR6SSS7JLYO7FR5AVCNFSM6AAAAABB5IZTSWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJVG44TKOBQGQ__;!!G2kpM7uM-TzIFchu!2cz6nRv-MDZHk-X9Ug3t3NvvS82bZv30wMxm_yybtZMypitsAPOCWi3A5ng7XwX4y76ul7r8vna3QHImzFRPGgc7jEU$>. You are receiving this because you authored the thread.Message ID: ***@***.***>