[clang] [lld] [llvm] [llvm][lld][clang] Delay initializing TargetOptions in LTO builds until a Triple is available (PR #179509)
Teresa Johnson via cfe-commits
cfe-commits at lists.llvm.org
Wed Feb 11 08:55:47 PST 2026
================
@@ -140,14 +141,17 @@ std::string llvm::computeLTOCacheKey(
Hasher.update(ArrayRef<uint8_t>(&I, 1));
};
AddString(Conf.CPU);
+ TargetOptions Opts = codegen::InitTargetOptionsFromCodeGenFlags(TT);
+ Conf.ModifyTargetOptions(Opts);
+
// FIXME: Hash more of Options. For now all clients initialize Options from
----------------
teresajohnson wrote:
Does this comment need an update (at least s/Options/TargetOptions/), and is it still valid? I.e. since this change initializes more of the TargetOptions from the Triple, are there more things that potentially need to be hashed. Or should the Triple itself be hashed?
https://github.com/llvm/llvm-project/pull/179509
More information about the cfe-commits
mailing list