Attachment 90688 Details for Bug 72619 – use i8 ptr instead of i32 ptr for load/store of mxcsr

[patch] use i8 ptr instead of i32 ptr for load/store of mxcsr

fpstate_i8ptr.diff (text/plain), 1.40 KB, created by Roland Scheidegger on 2013-12-13 02:58:50 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Roland Scheidegger

Created: 2013-12-13 02:58:50 UTC

Size: 1.40 KB

patch

obsolete

>diff --git a/src/gallium/auxiliary/gallivm/lp_bld_arit.c b/src/gallium/auxiliary/gallivm/lp_bld_arit.c
>index 440dd0b..e516ae8 100644
>--- a/src/gallium/auxiliary/gallivm/lp_bld_arit.c
>+++ b/src/gallium/auxiliary/gallivm/lp_bld_arit.c
>@@ -3510,10 +3510,12 @@ lp_build_fpstate_get(struct gallivm_state *gallivm)
>          gallivm,
>          LLVMInt32TypeInContext(gallivm->context),
>          "mxcsr_ptr");
>+      LLVMValueRef mxcsr_ptr8 = LLVMBuildPointerCast(builder, mxcsr_ptr,
>+          LLVMPointerType(LLVMInt8TypeInContext(gallivm->context), 0), "");
>       lp_build_intrinsic(builder,
>                          "llvm.x86.sse.stmxcsr",
>                          LLVMVoidTypeInContext(gallivm->context),
>-                         &mxcsr_ptr, 1);
>+                         &mxcsr_ptr8, 1);
>       return mxcsr_ptr;
>    }
>    return 0;
>@@ -3554,7 +3556,10 @@ lp_build_fpstate_set(struct gallivm_state *gallivm,
>                      LLVMValueRef mxcsr_ptr)
> {
>    if (util_cpu_caps.has_sse) {
>-      lp_build_intrinsic(gallivm->builder,
>+      LLVMBuilderRef builder = gallivm->builder;
>+      mxcsr_ptr = LLVMBuildPointerCast(builder, mxcsr_ptr,
>+                     LLVMPointerType(LLVMInt8TypeInContext(gallivm->context), 0), "");
>+      lp_build_intrinsic(builder,
>                          "llvm.x86.sse.ldmxcsr",
>                          LLVMVoidTypeInContext(gallivm->context),
>                          &mxcsr_ptr, 1);

Actions: View | Splinter Review

Attachments on bug 72619: 90688

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.