You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AndrewScull opened this issue
Sep 22, 2016
· 4 comments
Labels
A-codegenArea: Code generationA-LLVMArea: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.C-bugCategory: This is a bug.
Following the advice of rust-lang/rfcs#1364, I tried to avoid using SSE instructions by disabling MMX and SSE, and enabling soft-float with the features field of my tagert "features": "-mmx,-sse,+soft-float". However, when using an extern "win64" function for my UEFI entry point, movaps instructions are still generated to save and restore the xmm6-15 registers.
I have put together a minimal example to demonstate the problem.
The text was updated successfully, but these errors were encountered:
Mark-Simulacrum
added
C-bug
Category: This is a bug.
A-LLVM
Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.
labels
Jul 26, 2017
A-codegenArea: Code generationA-LLVMArea: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.C-bugCategory: This is a bug.
Following the advice of rust-lang/rfcs#1364, I tried to avoid using SSE instructions by disabling MMX and SSE, and enabling soft-float with the features field of my tagert "features": "-mmx,-sse,+soft-float". However, when using an extern "win64" function for my UEFI entry point, movaps instructions are still generated to save and restore the xmm6-15 registers.
I have put together a minimal example to demonstate the problem.
The text was updated successfully, but these errors were encountered: