michele-scandale wrote:
See https://github.com/llvm/llvm-project/pull/136038
https://github.com/llvm/llvm-project/pull/134159
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
michele-scandale wrote:
> There is already a precedent (hasPointerRepresentation) for not including
> vectors
You cannot have vectors of pointers in the C/C++ extensions for vector types.
> Also, vectors of Booleans have different considerations that scalar Booleans.
> For instance, they are
andykaylor wrote:
> Given that there are already similar functions in the `Type` class -- e.g.
> `has{Signed,Unsigned,}IntegerRepresentation`, `hasFloatingRepresentation` --
> it seems a bit inconsistent the definition of `hasBooleanRepresentation`. I
> would expect that "vector of booleans" t
michele-scandale wrote:
Given that there are already similar functions in the `Type` class -- e.g.
`has{Signed,Unsigned,}IntegerRepresentation`, `hasFloatingRepresentation` -- it
seems a bit inconsistent the definition of `hasBooleanRepresentation`. I would
expect that "vector of booleans" to
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Andy Kaylor (andykaylor)
Changes
The ClangIR upstreaming project needs the same logic for
hasBooleanRepresentation() that is currently implemented in the standard clang
codegen. In order to share this code, this change moves the implement
https://github.com/Sirraide approved this pull request.
https://github.com/llvm/llvm-project/pull/134159
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/andykaylor created
https://github.com/llvm/llvm-project/pull/134159
The ClangIR upstreaming project needs the same logic for
hasBooleanRepresentation() that is currently implemented in the standard clang
codegen. In order to share this code, this change moves the implementat
