Test path mapping with ThinLTO
i'm interested in testing this as well
This PR needs a rules_cc release with https://github.com/bazelbuild/rules_cc/commit/53b92d1bc57a5af745ef8968fba505a2210cd227
do both of those need to be on or just use_lto_native_object_directory?
As far as I can tell LTO by itself doesn't, but this test compiles generated files and thus needs the special feature.
one case i noticed the output paths were something like bazel-bin/path/to/binary.lto/bazel-out-k8-dbg-ST-whatever/path/to/artifact, i assume these aren't being stripped
Yeah, not yet. My plan was for this test to reproduce just that and then fix it.