Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
clang/lib/Headers/avx2intrin.h | ||
---|---|---|
1339 | It better to move it to \code{.operation} for consistency. Same for the below. |
clang/lib/Headers/avx2intrin.h | ||
---|---|---|
156 | My policy has been to provide the type for element sizes other than byte. So, I haven't been saying [32 x i8] but I do say [4 x i64] or whatever. | |
1339 | Okay. | |
1346 | Thanks for catching that! |
clang/lib/Headers/avx2intrin.h | ||
---|---|---|
456 | Intel intrinsics guide says dst[31:0] := a[31:0] - a[63:32] dst[63:32] := a[95:64] - a[127:96] dst[95:64] := b[31:0] - b[63:32] dst[127:96] := b[95:64] - b[127:96] dst[159:128] := a[159:128] - a[191:160] dst[191:160] := a[223:192] - a[255:224] dst[223:192] := b[159:128] - b[191:160] dst[255:224] := b[223:192] - b[255:224] dst[MAX:256] := 0 So I think the operands are in the wrong order here? | |
488 | Operands are reversed? |
Correct order of horizontal operands
clang/lib/Headers/avx2intrin.h | ||
---|---|---|
456 | Words fail me. Also diagrams. I wanted the add and sub descriptions to look similar, and copy-pasted from add to sub without verifying the order. |
clang/lib/Headers/avx2intrin.h | ||
---|---|---|
412 | I don't often see "underflow" applied to integer operations. Technically, any signed add or subtract could either overflow or underflow, depending on the sign and magnitude of the operands. I think just saying "overflow" is clear enough? | |
448 | The i31 is a typo, fixed. |
Why do some return descriptions include the type like [4 x i64] but some don't?