search for: x86mmx

Displaying 11 results from an estimated 11 matches for "x86mmx".

Did you mean: x86_mmx
2012 Nov 20
2
[LLVMdev] Extended Inline asm with double data type crashes clang
Hi, Clang crashes when below snippet of code is compiled (used latest svn version) *double func1() { double x ;* * asm ( "" : "=r"(x) : "0"(x) ); return x; }* > *clang -S test1.c* > *Assertion failed: (PartVT.isInteger() || PartVT == MVT::x86mmx) && ValueVT.isInteger() && "Unknown mismatch!", file ..\..\..\..\lib\CodeGen\SelectionDAG\SelectionDAGBuilder.cpp, line 378* Compilation sucessful, If data type passed to inline asm is of *float* * float x ;* * asm ( "" : "=r"(x) : "0"(x)...
2013 Sep 09
2
[LLVMdev] Intel Memory Protection Extensions (and types question)
Hi, On Monday, September 09, 2013 4:20 PM, Nadav Rotem [mailto:nrotem at apple.com] wrote: > Thanks for working on this. We usually try really hard to avoid adding new > types such as x86mmx. I don't know the memory-protection instruction set at > all but I imagine that you are not expecting other LLVM optimizations to > interact with them right ? (it looks that way from this example[1]). If you > are not accessing the individual components then you can use i128, or even...
2013 Sep 09
0
[LLVMdev] Intel Memory Protection Extensions (and types question)
Hi Kevin, Thanks for working on this. We usually try really hard to avoid adding new types such as x86mmx. I don’t know the memory-protection instruction set at all but I imagine that you are not expecting other LLVM optimizations to interact with them right ? (it looks that way from this example[1]). If you are not accessing the individual components then you can use i128, or even <2 x i64>....
2010 Dec 29
2
[LLVMdev] stack alignment restriction
Hi Is there a way to enforce a different alignment on vales on stack as compared to other basic types. Particularly, i would like characters to be stored at 2 byte boundary. thanks dz
2010 Dec 29
0
[LLVMdev] stack alignment restriction
...out examples in the lib/Target/* directories. For instance in X86CallingConv.td, we have things like this: def CC_X86_64_C : CallingConv<[ ... // __m64 vectors get 8-byte stack slots that are 8-byte aligned. CCIfType<[x86mmx,v1i64], CCAssignToStack<8, 8>> } The second parameter to CCAssigneToStack is the alignment for that type. -bw
2010 Dec 29
1
[LLVMdev] stack alignment restriction
...te boundary. >> > Check out examples in the lib/Target/* directories. For instance in X86CallingConv.td, we have things like this: > > def CC_X86_64_C : CallingConv<[ > ... >  // __m64 vectors get 8-byte stack slots that are 8-byte aligned. >  CCIfType<[x86mmx,v1i64], CCAssignToStack<8, 8>> > } > > The second parameter to CCAssigneToStack is the alignment for that type. > > -bw > >
2012 Nov 20
0
[LLVMdev] Extended Inline asm with double data type crashes clang
...ow snippet of code is compiled (used latest svn > version) > > double func1() > { > double x ; > asm ( "" : "=r"(x) : "0"(x) ); > return x; > } > >> clang -S test1.c >> Assertion failed: (PartVT.isInteger() || PartVT == MVT::x86mmx) && >> ValueVT.isInteger() && "Unknown mismatch!", file >> ..\..\..\..\lib\CodeGen\SelectionDAG\SelectionDAGBuilder.cpp, line 378 > > > Compilation sucessful, If data type passed to inline asm is of float > float x ; > asm ( "" : &q...
2012 Nov 21
2
[LLVMdev] Extended Inline asm with double data type crashes clang
...t; version) > > > > double func1() > > { > > double x ; > > asm ( "" : "=r"(x) : "0"(x) ); > > return x; > > } > > > >> clang -S test1.c > >> Assertion failed: (PartVT.isInteger() || PartVT == MVT::x86mmx) && > >> ValueVT.isInteger() && "Unknown mismatch!", file > >> ..\..\..\..\lib\CodeGen\SelectionDAG\SelectionDAGBuilder.cpp, line 378 > > > > > > Compilation sucessful, If data type passed to inline asm is of float > > float x ;...
2013 Sep 10
0
[LLVMdev] Intel Memory Protection Extensions (and types question)
...9, 2013, at 2:00 PM, Schoedel, Kevin P <kevin.p.schoedel at intel.com> wrote: > Hi, > > On Monday, September 09, 2013 4:20 PM, Nadav Rotem [mailto:nrotem at apple.com] wrote: >> Thanks for working on this. We usually try really hard to avoid adding new >> types such as x86mmx. I don't know the memory-protection instruction set at >> all but I imagine that you are not expecting other LLVM optimizations to >> interact with them right ? (it looks that way from this example[1]). If you >> are not accessing the individual components then you can use i...
2013 Sep 09
4
[LLVMdev] Intel Memory Protection Extensions (and types question)
Hi all, I'm currently adding new instructions and registers to the X86 code generator for Intel Memory Protection Extensions [1]. A class of special-purpose registers BNDx each holds 2 x 64-bit values. The components are not individually readable or writable (except by going through memory) but there are instructions that read only one of the two elements. The two 64-bit values can be
2012 Nov 22
0
[LLVMdev] Extended Inline asm with double data type crashes clang
...double func1() >> > { >> > double x ; >> > asm ( "" : "=r"(x) : "0"(x) ); >> > return x; >> > } >> > >> >> clang -S test1.c >> >> Assertion failed: (PartVT.isInteger() || PartVT == MVT::x86mmx) && >> >> ValueVT.isInteger() && "Unknown mismatch!", file >> >> ..\..\..\..\lib\CodeGen\SelectionDAG\SelectionDAGBuilder.cpp, line 378 >> > >> > >> > Compilation sucessful, If data type passed to inline asm is of float &g...