fix llvm-kompile being passed more options conventionally (#4514)

This changes the order of flags passed to llvm-kompile in order to ensure that llvm-kompile-codegen will run with the correct optimization flags. Co-authored-by: rv-jenkins <[email protected]>
runtimeverification · Jul 11, 2024 · d90b8b1 · d90b8b1
1 parent f807c22
commit d90b8b1
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/llvm-backend/src/main/java/org/kframework/backend/llvm/LLVMBackend.java b/llvm-backend/src/main/java/org/kframework/backend/llvm/LLVMBackend.java
@@ -143,9 +143,6 @@ private void llvmKompile(String type, String executable) {
         args.add("--mutable-bytes");
       }
 
-      // Arguments after this point are passed on to Clang.
-      args.add("--");
-
       if (options.debug) {
         args.add("-g");
         args.add("-O1");
@@ -171,6 +168,9 @@ private void llvmKompile(String type, String executable) {
           args.add("-O2"); // clang -O3 does not make the llvm backend any faster
       }
 
+      // Arguments after this point are passed on to Clang.
+      args.add("--");
+
       args.addAll(options.ccopts);
 
       if (globalOptions.verbose) {