Adds type trait "__builtin_omp_required_simd_align" after discussions here http://reviews.llvm.org/D9894
Details
- Reviewers
rjmccall - Commits
- rG003965130462: [OPENMP] Introduced type trait "__builtin_omp_required_simd_align" for default…
rC241237: [OPENMP] Introduced type trait "__builtin_omp_required_simd_align" for default…
rL241237: [OPENMP] Introduced type trait "__builtin_omp_required_simd_align" for default…
Diff Detail
Event Timeline
include/clang/AST/ASTContext.h | ||
---|---|---|
85 | Just make this a separate query on ASTContext. TypeInfo computation is important to a lot of different clients, basically none of which care about this. I don't think it's important to cache. | |
include/clang/Basic/TokenKinds.def | ||
507 | This is a very general name to give this, and putting it in the unreserved namespace is problematic. I think that, given some time and coordination, we could design a more general "what's the largest supported vector type for this underlying type" query, and that would justify a name like this. But the existing vector attributes always talk about, well, "vector" instead of "simd"; and anyway, it's not obvious that the answer to that general query would necessarily dictate the answer to this OpenMP-specific one. So let's design this as a more targeted feature around the needs of OpenMP. In that context, "simd" is fine because it's exactly the name of the OpenMP feature. How about "builtin_openmp_simd_align"? Or even "builtin_openmp_required_simd_align"? | |
lib/AST/ItaniumMangle.cpp | ||
3024 | Copy-paste error. | |
lib/Basic/Targets.cpp | ||
2979 | Aren't we saying that this is 64 for AVX512? | |
lib/CodeGen/CGExprScalar.cpp | ||
2044 | This needs to produce a size_t, not an int32_t. You can use CGM::getSize. | |
lib/Sema/SemaExpr.cpp | ||
3522 | This should be a hard error, not just an extension warning. | |
3829 | Hmm. Thinking more about it, using this trait with an expression instead of a type seems pretty misleading. Let's make this a hard error for now. We can continue to use the UETT parsing logic and AST representation. |
John, thank you for the review!
include/clang/AST/ASTContext.h | ||
---|---|---|
85 | Ok, will separate it. | |
include/clang/Basic/TokenKinds.def | ||
507 | Ok, turned it to __builtin_omp_required_simd_align. Actually, I thought about such kind of name, but it was too long, so I changed it to a shorter version. :) | |
lib/AST/ItaniumMangle.cpp | ||
3024 | Fixed, thanks | |
lib/Basic/Targets.cpp | ||
2979 | There were no "avx512" defined when I prepared a patch. Will be added | |
lib/CodeGen/CGExprScalar.cpp | ||
2044 | Thanks, fixed | |
lib/Sema/SemaExpr.cpp | ||
3522 | Will be removed it and expressions won't be allowed as arguments | |
3829 | Ok |
"omp" instead of "openmp" makes a lot sense, since that's what's used in the pragma.
include/clang/Basic/DiagnosticSemaKinds.td | ||
---|---|---|
4688 | You lost the 0 here. | |
include/clang/Basic/TargetInfo.h | ||
397 | Please embellish this comment to make it clear that it's sometimes type-specific. It would be great if we could move the type-specific logic to TargetInfo, but I don't know of a way to do that without either (1) making a lot of assumptions about what kinds of types are interesting to the target or (2) creating a cyclic dependency between lib/Basic and lib/AST. Ugh. We can stick with what we have right now. | |
lib/AST/ASTContext.cpp | ||
1791 | I think this query should probably apply to the underlying type, not to the pointer type. That is, if I want to know the expected alignment of an array of doubles, I should use __builtin_omp_required_simd_align(double) not __builtin_omp_required_simd_align(double*) Unless PPC64's rule really is about arrays of pointers to double? | |
lib/CodeGen/CGExprScalar.cpp | ||
2045 | I assume the type of the argument here is always a pointer, which means you'll need to drill down to the element type. | |
lib/Parse/ParseExpr.cpp | ||
1046 | These comments are supposed to be grammar specifications; whoever implemented vec_step apparently missed that. What you want is: unary-expression: '__builtin_omp_required_simd_align' '(' type-name ')' (since we don't actually allow the expression form semantically) |
One more tweak, and then LGTM.
include/clang/Basic/TypeTraits.h | ||
---|---|---|
96 | Please rename this to follow the actual name of the trait, i.e. UETT_OpenMPRequiredSimdAlign. |
Just make this a separate query on ASTContext. TypeInfo computation is important to a lot of different clients, basically none of which care about this.
I don't think it's important to cache.