search for: __spir_sizet_convert_size_t

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

2012 Sep 12
2
[LLVMdev] [cfe-dev] SPIR Portability Discussion
...previous > email, > > "sizeof(sizeof(int))" should have been size_t(sizeof(int)), which was > > throwing me off. I view this case as being well defined in SPIR. It > can be > > produced with something like the following: > > > > %0 = call %spir.size_t @__spir_sizet_convert_size_t(i32 0) > > > > %1 = call %spir.size_t @__spir_sizet_convert_size_t(i32 4) > > > > %2 = call %spir.size_t @__spir_sizet_convert_size_t(i64 8) > > > > %3 = call %spir.size_t @__spir_sizet_neg(%spir.size_t %2) > > > > %4 = call %spir.size_t @__spir_sizet...
2012 Sep 12
0
[LLVMdev] [cfe-dev] SPIR Portability Discussion
...h] I see now, I think you had a type-o in the previous email, > “sizeof(sizeof(int))” should have been size_t(sizeof(int)), which was > throwing me off. I view this case as being well defined in SPIR. It can be > produced with something like the following: > > %0 = call %spir.size_t @__spir_sizet_convert_size_t(i32 0) > > %1 = call %spir.size_t @__spir_sizet_convert_size_t(i32 4) > > %2 = call %spir.size_t @__spir_sizet_convert_size_t(i64 8) > > %3 = call %spir.size_t @__spir_sizet_neg(%spir.size_t %2) > > %4 = call %spir.size_t @__spir_sizet_add(%spir.size_t %1, %spir.size_t %3) &...
2012 Sep 12
0
[LLVMdev] [cfe-dev] SPIR Portability Discussion
...t;> > "sizeof(sizeof(int))" should have been size_t(sizeof(int)), which was >> > throwing me off. I view this case as being well defined in SPIR. It >> can be >> > produced with something like the following: >> > >> > %0 = call %spir.size_t @__spir_sizet_convert_size_t(i32 0) >> > >> > %1 = call %spir.size_t @__spir_sizet_convert_size_t(i32 4) >> > >> > %2 = call %spir.size_t @__spir_sizet_convert_size_t(i64 8) >> > >> > %3 = call %spir.size_t @__spir_sizet_neg(%spir.size_t %2) >> > >> > %4 =...
2012 Sep 12
4
[LLVMdev] [cfe-dev] SPIR Portability Discussion
...[Villmow, Micah] I see now, I think you had a type-o in the previous email, "sizeof(sizeof(int))" should have been size_t(sizeof(int)), which was throwing me off. I view this case as being well defined in SPIR. It can be produced with something like the following: %0 = call %spir.size_t @__spir_sizet_convert_size_t(i32 0) %1 = call %spir.size_t @__spir_sizet_convert_size_t(i32 4) %2 = call %spir.size_t @__spir_sizet_convert_size_t(i64 8) %3 = call %spir.size_t @__spir_sizet_neg(%spir.size_t %2) %4 = call %spir.size_t @__spir_sizet_add(%spir.size_t %1, %spir.size_t %3) %5 = call %spir.size_t @__spir_sizet_cmp(...
2012 Sep 12
0
[LLVMdev] [cfe-dev] SPIR Portability Discussion
On Wed, Sep 12, 2012 at 3:26 PM, Villmow, Micah <Micah.Villmow at amd.com>wrote: > > > > -----Original Message----- > > From: Eli Friedman [mailto:eli.friedman at gmail.com] > > Sent: Wednesday, September 12, 2012 3:22 PM > > To: Villmow, Micah > > Cc: Richard Smith; cfe-dev at cs.uiuc.edu; llvmdev at cs.uiuc.edu > > Subject: Re: [cfe-dev] [LLVMdev]
2012 Sep 12
2
[LLVMdev] [cfe-dev] SPIR Portability Discussion
> -----Original Message----- > From: Eli Friedman [mailto:eli.friedman at gmail.com] > Sent: Wednesday, September 12, 2012 3:22 PM > To: Villmow, Micah > Cc: Richard Smith; cfe-dev at cs.uiuc.edu; llvmdev at cs.uiuc.edu > Subject: Re: [cfe-dev] [LLVMdev] SPIR Portability Discussion > > On Wed, Sep 12, 2012 at 2:58 PM, Villmow, Micah <Micah.Villmow at amd.com> >
2012 Sep 12
2
[LLVMdev] SPIR Portability Discussion
...enCL 1.2 (6.3)/k says the result of sizeof is an ICE. So these are valid: int does_this_compile[sizeof(void*) - 3]; [Villmow, Micah] 'ICE'? Integer compile time expression? While not pretty, this can be represented in SPIR with the following sequence on instructions %1 = call %spir.size_t @__spir_sizet_convert_size_t(i32 3) %2 = call %spir.size_t @__spir_size_of_sizet() %3 = call %spir.size_t @__spir_sizet_sub(%spir.size_t %1, %spir.size_t %2) %4 = call %spir.size_t @__spir_sizet_convert_i32(%spir.size_t %3) %5 = alloca i32, i32 %4 struct how_do_you_represent_this_in_IR { int a : 1; int b : sizeof(void*) *...
2012 Sep 12
0
[LLVMdev] SPIR Portability Discussion
...nt does_this_compile[sizeof(void*) - 3]; > Oops, I meant sizeof(void*) - 5. > **** > > *[Villmow, Micah] ‘ICE’? Integer compile time expression? While not > pretty, this can be represented in SPIR with the following sequence on > instructions* > > *%1 = call %spir.size_t @__spir_sizet_convert_size_t(i32 3)* > > *%2 = call %spir.size_t @__spir_size_of_sizet()* > > *%3 = call %spir.size_t @__spir_sizet_sub(%spir.size_t %1, %spir.size_t > %2)* > > *%4 = call %spir.size_t @__spir_sizet_convert_i32(%spir.size_t %3)* > > *%5 = alloca i32, i32 %4* > My point here was th...
2012 Sep 12
3
[LLVMdev] SPIR Portability Discussion
...sizeof is an ICE. So these are valid: int does_this_compile[sizeof(void*) - 3]; Oops, I meant sizeof(void*) - 5. [Villmow, Micah] 'ICE'? Integer compile time expression? While not pretty, this can be represented in SPIR with the following sequence on instructions %1 = call %spir.size_t @__spir_sizet_convert_size_t(i32 3) %2 = call %spir.size_t @__spir_size_of_sizet() %3 = call %spir.size_t @__spir_sizet_sub(%spir.size_t %1, %spir.size_t %2) %4 = call %spir.size_t @__spir_sizet_convert_i32(%spir.size_t %3) %5 = alloca i32, i32 %4 My point here was that if sizeof(void*) is an integer constant expression, then...
2012 Sep 12
0
[LLVMdev] SPIR Portability Discussion
On Wed, Sep 12, 2012 at 12:27 PM, Ouriel, Boaz <boaz.ouriel at intel.com>wrote: > Hey All, > > This is a very big topic in SPIR and probably a very controversial one as > well. It includes dealing with 32 vs. 64 bit architectures and OpenCL "C" > endianness. > We have written down some of the aspects, but of course did not cover > everything - let's start
2012 Sep 12
5
[LLVMdev] SPIR Portability Discussion
Hey All, This is a very big topic in SPIR and probably a very controversial one as well. It includes dealing with 32 vs. 64 bit architectures and OpenCL "C" endianness. We have written down some of the aspects, but of course did not cover everything - let's start a discussion on the portability and see where it takes us. I suggest we start with the 32 vs. 64 bits discussion and then