| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | [x86] AVX FP compare builtins should require AVX target feature (PR28112) | Sanjay Patel | 2016-06-21 | 1 | -1/+32 | 
| | | | | | | | | | | | | | | | | | | This is a fix for PR28112: https://llvm.org/bugs/show_bug.cgi?id=28112 The FP comparison intrinsics that take an immediate parameter (rather than specifying a comparison predicate in the function name) were added with AVX; these are macros in avxintrin.h. This patch makes clang behavior match gcc (error if a program tries to use these without -mavx) and matches the Intel documentation, eg: VCMPPS: m128 _mm_cmp_ps(m128 a, __m128 b, const int imm) 'V' means this is intended to only work with the AVX form of the instruction. Differential Revision: http://reviews.llvm.org/D21306 llvm-svn: 273311 | ||||
| * | Add support for the always_inline + target feature diagnostic to print | Eric Christopher | 2015-11-14 | 1 | -1/+1 | 
| | | | | | | | | out the first missing target feature that's required and reword the diagnostic accordingly. llvm-svn: 253121 | ||||
| * | Provide a frontend based error for always_inline functions that require | Eric Christopher | 2015-11-12 | 1 | -0/+7 | 
| target features that the caller function doesn't provide. This matches the existing backend failure to inline functions that don't have matching target features - and diagnoses earlier in the case of always_inline. Fix up a few test cases that were, in fact, invalid if you tried to generate code from the backend with the specified target features and add a couple of tests to illustrate what's going on. This should fix PR25246. llvm-svn: 252834 | |||||

