ychen added a comment.
Sorry for the confusion @steven_wu. By `stable` I mean the probability that the
`-fthin-link-bitcode` option is replaced with some other thinlink mechanism
under the distributed build environment. Since at least for ccache, the
compilation output caching depends on the semantics of options ("-o" is assumed
to be compilation output). For the case of `-fthin-link-bitcode`, both
`-Xclang -fthin-link-bitcode` and `-o` are the output. I'm not familiar with
compiler cache tools, but having the caching depends on a cc1 option feels not
right since it is not an option of any other compilers, so most caching tools
don't recognize it.
Repository:
rG LLVM Github Monorepo
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D69327/new/
https://reviews.llvm.org/D69327
_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
