search for: ouriel

From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Richard Smith Sent: Wednesday, September 12, 2012 1:55 PM To: Ouriel, Boaz Cc: cfe-dev at cs.uiuc.edu; llvmdev at cs.uiuc.edu Subject: Re: [LLVMdev] SPIR Portability Discussion On Wed, Sep 12, 2012 at 12:27 PM, Ouriel, Boaz <boaz.ouriel at intel.com<mailto:boaz.ouriel at intel.com>> wrote: Hey All, This is a very big topic in SPIR and probably a very c...

...n Wed, Sep 12, 2012 at 2:23 PM, Villmow, Micah <Micah.Villmow at amd.com>wrote: > ** ** > > ** ** > > *From:* llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] *On > Behalf Of *Richard Smith > *Sent:* Wednesday, September 12, 2012 1:55 PM > *To:* Ouriel, Boaz > *Cc:* cfe-dev at cs.uiuc.edu; llvmdev at cs.uiuc.edu > *Subject:* Re: [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 top...

From: metafoo at gmail.com [mailto:metafoo at gmail.com] On Behalf Of Richard Smith Sent: Wednesday, September 12, 2012 2:51 PM To: Villmow, Micah Cc: Ouriel, Boaz; cfe-dev at cs.uiuc.edu; llvmdev at cs.uiuc.edu Subject: Re: [LLVMdev] SPIR Portability Discussion On Wed, Sep 12, 2012 at 2:23 PM, Villmow, Micah <Micah.Villmow at amd.com<mailto:Micah.Villmow at amd.com>> wrote: From: llvmdev-bounces at cs.uiuc.edu<mailto:llvmdev-bounces a...

...e ABI compliance contract), I'm not sure how a new LLVM calling convention helps remove platform dependence. Although I may have missed a/the point somewhere along the line, I've been a bit ill in recent days and not fully engaged, brain-wise :) Cheers, James On 12 September 2012 19:54, Ouriel, Boaz <boaz.ouriel at intel.com> wrote: > Hi James, > > This is very good feedback. > > 1. Adding the new calling conventions - It seems like the appropriate thing to do vs. metadata. Some OpenCL backends can choose to implement this calling convention and use it during code ge...

...izations incompatible with SPIR. Let me discuss this a bit further in Khronos and come back with additional feedback. Thanks, Boaz -----Original Message----- From: mankeyrabbit at gmail.com [mailto:mankeyrabbit at gmail.com] On Behalf Of James Molloy Sent: Wednesday, September 12, 2012 11:08 To: Ouriel, Boaz Cc: cfe-dev at cs.uiuc.edu; llvmdev at cs.uiuc.edu; Villmow, Micah Subject: Re: [cfe-dev] [LLVMdev] SPIR provisional specification is now available in the Khronos website Hi Boaz, Micah, Thanks for the followup. > I agree with Micah that optimizing a SPIR module might make it less porta...

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, bu...

On Sep 6, 2012, at 4:33 PM, "Ouriel, Boaz" <boaz.ouriel at intel.com> wrote: > **** Introduction **** > Lately, Khronos has ratified a new provisional specification which is called SPIR. > This specification standardizes an intermediate representation for the OpenCL kernel language. > It is based on LLVM infr...

> -----Original Message----- > From: mankeyrabbit at gmail.com [mailto:mankeyrabbit at gmail.com] On Behalf > Of James Molloy > Sent: Wednesday, September 12, 2012 12:18 PM > To: Ouriel, Boaz > Cc: cfe-dev at cs.uiuc.edu; llvmdev at cs.uiuc.edu; Villmow, Micah > Subject: Re: [cfe-dev] [LLVMdev] SPIR provisional specification is now > available in the Khronos website > > Hi Boaz, David, > > Thanks for taking my responses on board. > > > 1. Adding th...

...nerator having to make ABI decisions. Not only that, but for valid codegen any backend is going to have to remove those calling convention markers anyway and replace them with their own, so why have them in the first place? I've rambled slightly, sorry about that! On 12 September 2012 00:00, Ouriel, Boaz <boaz.ouriel at intel.com> wrote: > Hi James, > > some additional comments regarding some of your questions: > Q: Is SPIR meant to be storage-only, or to allow optimizations to be done? > > I agree with Micah that optimizing a SPIR module might make it less portable. &...

...al to access by OpenCL optimizers. Does this make sense? Do you see an issue with adding the suggested calling conventions? Thanks, Boaz -----Original Message----- From: Villmow, Micah [mailto:Micah.Villmow at amd.com] Sent: Wednesday, September 12, 2012 00:03 To: James Molloy Cc: James Molloy; Ouriel, Boaz; cfe-dev at cs.uiuc.edu; llvmdev at cs.uiuc.edu Subject: RE: [cfe-dev] [LLVMdev] SPIR provisional specifciation is now available in the Khronos website > -----Original Message----- > From: mankeyrabbit at gmail.com [mailto:mankeyrabbit at gmail.com] On Behalf > Of James Molloy &gt...

...du [mailto:llvmdev-bounces at cs.uiuc.edu] > On Behalf Of Vikram Adve > Sent: Thursday, September 06, 2012 3:52 PM > To: llvmdev at cs.uiuc.edu > Subject: Re: [LLVMdev] "SPIR" ? A Standard Portable IR for OpenCL > Kernel Language > > On Sep 6, 2012, at 4:33 PM, "Ouriel, Boaz" <boaz.ouriel at intel.com> > wrote: > > > **** Introduction **** > > Lately, Khronos has ratified a new provisional specification which is > called SPIR. > > This specification standardizes an intermediate representation for > the OpenCL kernel langu...

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

Hi All, Today, LLVM IR doesn't include a description for alignment for specific data members inside structures. The implies that LLVM IR Generators need to do the padding themselves in order to achieve the requested alignment. Since the information is not represented explicitly by the LLVM IR, optimization passes might unintentionally break the required alignment and lead to unexpected

...that difficult to lower global variables to function arguments given SPIR representation. Micah > -----Original Message----- > From: Carlos Sánchez de La Lama [mailto:csanchezdll at gmail.com] > Sent: Friday, September 28, 2012 12:34 AM > To: James Molloy > Cc: Pekka Jääskeläinen; Ouriel, Boaz; pocl-devel at lists.sourceforge.net; > Villmow, Micah; cfe-dev at cs.uiuc.edu; llvmdev at cs.uiuc.edu > Subject: Re: [pocl-devel] [cfe-dev] [LLVMdev] SPIR provisional > specification is now available in the Khronos website > > Hi guys, > > > So it is valid SPIR, as...

> -----Original Message----- > From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] > On Behalf Of James Molloy > Sent: Tuesday, September 11, 2012 8:49 AM > To: Ouriel, Boaz > Cc: cfe-dev at cs.uiuc.edu; llvmdev at cs.uiuc.edu > Subject: Re: [LLVMdev] SPIR provisional specifciation is now available > in the Khronos website > > Hi Boaz, > > I have a couple of specific questions: > > (a) You mention special calling conventions and addi...

...r 2012 16:54, Villmow, Micah <Micah.Villmow at amd.com> wrote: > > >> -----Original Message----- >> From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] >> On Behalf Of James Molloy >> Sent: Tuesday, September 11, 2012 8:49 AM >> To: Ouriel, Boaz >> Cc: cfe-dev at cs.uiuc.edu; llvmdev at cs.uiuc.edu >> Subject: Re: [LLVMdev] SPIR provisional specifciation is now available >> in the Khronos website >> >> Hi Boaz, >> >> I have a couple of specific questions: >> >> (a) You mention spe...

Hi Boaz, I have a couple of specific questions: (a) You mention special calling conventions and adding them to LLVM. What are their semantics? And what is their purpose? (b) Why disallow type conversion for vector types? (ss. 3.3) Cheers, James On Tue, 2012-09-11 at 12:56 +0100, Ouriel, Boaz wrote: > Hi All, > > In continuation of the previous SPIR introduction email here is a link to the specification: > http://www.khronos.org/registry/cl/specs/spir_spec-1.0-provisional.pdf > > The first topic which we would like to discuss is "SPIR portability". &g...

...e would like to discuss is "SPIR portability". I will send soon an additional mail which will help in leading the discussion on this topic. Thanks and happy reading, Boaz -----Original Message----- From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Ouriel, Boaz Sent: Thursday, September 06, 2012 22:06 To: cfe-dev at cs.uiuc.edu; llvmdev at cs.uiuc.edu Subject: [LLVMdev] "SPIR" - A Standard Portable IR for OpenCL Kernel Language Greetings All, I am sending this mail on behalf of the OpenCL Khronos members. **** Introduction **** Lately,...

...les to function arguments given SPIR representation. > > Micah > > > -----Original Message----- > > From: Carlos Sánchez de La Lama [mailto:csanchezdll at gmail.com] > > Sent: Friday, September 28, 2012 12:34 AM > > To: James Molloy > > Cc: Pekka Jääskeläinen; Ouriel, Boaz; pocl-devel at lists.sourceforge.net; > > Villmow, Micah; cfe-dev at cs.uiuc.edu; llvmdev at cs.uiuc.edu > > Subject: Re: [pocl-devel] [cfe-dev] [LLVMdev] SPIR provisional > > specification is now available in the Khronos website > > > > Hi guys, > > > &...

On Wed, Sep 19, 2012 at 5:43 AM, Benyei, Guy <guy.benyei at intel.com> wrote: > Ouriel, Boaz wrote: > > > ... > > > *** Richard Smith, Eli Friedman & Nadav Rotem: Portability Issues *** > > *****comment 1: int does_this_compile[sizeof(void*) - 3]; > Answer: We are discussing this internally and will provide an answer soon....