From: Bill Wendling Date: Tue, 21 Sep 2010 01:39:34 +0000 (+0000) Subject: Add a comment explaining why the MMX builtins are segregated and what we plan on X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=2e81caa14337cfa8973a1a073ef4dbbb8273238c;p=clang Add a comment explaining why the MMX builtins are segregated and what we plan on doing with them. It's a "FIXME" right now because this change hasn't been implemented yet. git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@114385 91177308-0d34-0410-b5e6-96231b3b80d8 --- diff --git a/include/clang/Basic/BuiltinsX86.def b/include/clang/Basic/BuiltinsX86.def index 955e71c30e..025e7b60c2 100644 --- a/include/clang/Basic/BuiltinsX86.def +++ b/include/clang/Basic/BuiltinsX86.def @@ -25,6 +25,10 @@ // FIXME: Are these nothrow/const? // MMX +// +// FIXME: All MMX instructions will be generated via builtins. Any MMX vector +// types (<1 x i64>, <2 x i32>, etc.) that aren't used by these builtins will be +// expanded by the back-end. BUILTIN(__builtin_ia32_emms, "v", "") BUILTIN(__builtin_ia32_femms, "v", "") BUILTIN(__builtin_ia32_paddb, "V8cV8cV8c", "")