[llvm] [DirectX] Set Shader Flag DisableOptimizations. (PR #123136)

[Chris B via llvm-commits]

================
@@ -68,6 +68,37 @@ static ModuleMetadataInfo collectMetadataInfo(Module &M) {
     }
     MMDAI.EntryPropertyVec.push_back(EFP);
   }
+
+  // Set shader flags based on Module properties
+  SmallVector<llvm::Module::ModuleFlagEntry> FlagEntries;
+  SmallVector<llvm::Module::ModuleFlagEntry> NewFlagEntries;
+  M.getModuleFlagsMetadata(FlagEntries);
+  for (const auto &Flag : FlagEntries) {
+    if ((Flag.Behavior == Module::ModFlagBehavior::Override) &&
+        (Flag.Key->getString().compare("dx.disable_optimizations") == 0)) {
+      const auto *V = mdconst::extract<llvm::ConstantInt>(Flag.Val);
+      if (V->isOne())
+        MMDAI.DisableOptimizations = true;
+    } else
+      // Collect all Module Flags other than dx.disable_optimizations.
+      NewFlagEntries.push_back(Flag);
+  }
+
+  // "dx.disable_optimizations" is not included in the metadata specified in
+  // DXIL specification. Hence it needs to be deleted such that it is not
+  // emitted in the final DXIL output, now that its intent is captured in MMDAI,
+  // if present.
+
+  if (NewFlagEntries.size() != FlagEntries.size()) {
----------------
llvm-beanz wrote:

Do we need to do this here? We have code in DXILPrepare that cleans the module flags.

@bogner, I think the reason the `dx.disable_optimizations` named metadata wasn't causing issues is because DXIL doesn't use custom module flags at all, so in DXILPrepare we just strip out any non-standard LLVM 3.7 module flags, which will clean this up.

https://github.com/llvm/llvm-project/pull/123136