diff options
Diffstat (limited to 'community/postgresql12/jit-Don-t-use-host-specific-CPU-or-features.patch')
| -rw-r--r-- | community/postgresql12/jit-Don-t-use-host-specific-CPU-or-features.patch | 27 |
1 files changed, 0 insertions, 27 deletions
diff --git a/community/postgresql12/jit-Don-t-use-host-specific-CPU-or-features.patch b/community/postgresql12/jit-Don-t-use-host-specific-CPU-or-features.patch deleted file mode 100644 index 94076de622d..00000000000 --- a/community/postgresql12/jit-Don-t-use-host-specific-CPU-or-features.patch +++ /dev/null @@ -1,27 +0,0 @@ ---- a/src/backend/jit/llvm/llvmjit.c -+++ b/src/backend/jit/llvm/llvmjit.c -@@ -815,10 +815,20 @@ - * latter is needed because some CPU architectures default to enabling - * features not all CPUs have (weird, huh). - */ -- cpu = LLVMGetHostCPUName(); -- features = LLVMGetHostCPUFeatures(); -- elog(DEBUG2, "LLVMJIT detected CPU \"%s\", with features \"%s\"", -- cpu, features); -+ -+ /* FIXME: When compile code to pass to the JIT, we are pulling the -+ -+ * datalayout from the llvmjit_types.bc, which is compiled at build -+ -+ * type without any specifc CPU or feature flags. This can lead to -+ -+ * a mismatch between the JIT's datalayout and the code's datalayout -+ -+ * if we initialize the JIT for a specific CPU. So for now don't use -+ -+ * any host specific cpu features when creating the JIT. -+ -+ */ - - opt0_tm = - LLVMCreateTargetMachine(llvm_targetref, llvm_triple, cpu, features, |