SGX示例应用编译失败：_mm_lfence标识符未找到求助

Hey there, let's work through this issue you're hitting. The _mm_lfence is an Intel memory fence instruction used in SGX code to enforce memory access ordering, and this "identifier not found" error almost always comes down to misconfigured build settings—not your sign function returning nullptr (that part doesn't affect the compilation of auto-generated proxy code). Here are the key troubleshooting steps:

1. Verify Compiler Instruction Set Support #

_mm_lfence is part of the SSE2 instruction set extension, so MSVC needs explicit enablement:

• Right-click your project → Properties → Configuration Properties → C/C++ → Code Generation → Enable Enhanced Instruction Set → select SSE2 or a higher option (like AVX2)
• Alternatively, add this pragma at the top of your source files: #pragma target("sse2"), but configuring via project properties is more reliable for consistent builds.

2. Check SGX SDK Path & Version Compatibility #

The auto-generated SGX proxy code relies on SDK headers (like sgx_isa.h) that define _mm_lfence. If the SDK path isn't set correctly, the compiler can't find these definitions:

• Confirm your project's VC++ Directories → Include Directories includes the SGX SDK's include path (e.g., C:\Program Files\Intel\SGXSDK\include)
• Make sure your SGX SDK version matches the Visual Studio SGX plugin you're using—version mismatches often cause missing or incompatible header files.

3. Ensure Consistent Build Platform & Mode #

SGX apps have two core components (Enclave and untrusted App), so their build configurations need to align perfectly:

• Double-check that your project's Platform is set to x64 (SGX primarily supports 64-bit; mixing x86/x64 will cause unexpected errors)
• Verify that your Enclave project has the correct SGX mode defined (SGX_MODE=SIMULATION or SGX_MODE=HW) in its preprocessor directives.

4. Temporary Fix: Explicitly Include the Intrinsics Header #

If all configuration checks pass and you still see the error, you can manually add this include at the top of the auto-generated proxy header files (usually named [your_edl]_u.h or [your_edl]_t.h):

#include <intrin.h>

This header directly defines _mm_lfence, but this is a band-aid solution—focus on fixing the root configuration issue for long-term stability.

Just to clarify again: Your sign function returning nullptr has no bearing on this compilation error, since the proxy code is generated independently of your function's implementation.

内容的提问来源于stack exchange，提问作者Fylax