nvcc fails when uncacheable

[charlie-rivos]

Instead of doing an uncached compilation and logging that the compilation was uncacheable, sccache exits when it encounters uncacheable nvcc args.

The code responsible is here:

sccache/src/compiler/nvcc.rs

Line 1282 in 9fb3841

CompilerArguments::CannotCache(why, extra_info) => Err(extra_info

This behavior prevents users from using sccache when there happens to be a program with uncacheable args.

[charlie-rivos]

@trxcllnt

[trxcllnt]

@charlie-rivos which arguments are failing to parse? nvcc has many arguments not explicitly enumerated in sccache, but you can usually work around it by using = as the separator, e.g. -diag-suppress=1407 instead of -diag-suppress 1407.

[charlie-rivos]

Oh that's embarrassing, thank you that was the issue. I guess the CanBeSeparated logic doesn't quite work as intended?

This behavior still seems somewhat surprising to have sccache crash if it encounters an uncacheable compilation. I believe other parts of sccache log a compilation attempt as uncacheable and fall back to doing an uncached compilation in this case instead of aborting. Is there a reason to have nvcc abort instead of performing a fallback?