search for: stream_executor

...to moderate the new mailing lists. We will want a website. I think there will be a top-level docs directory for the project and a docs directory for each subproject. To begin with, StreamExecutor will be the only subproject so the structure will look something like this: parallel-libs/ docs/ stream_executor/ docs/ Does that seem like a reasonable way to set it up? On Wed, Jun 15, 2016 at 8:44 PM Tanya Lattner <tanyalattner at llvm.org> wrote: > Jason, > > This sounds good. Have you created the project in SVN yet? > > I’ll need to do the post commit hook to the mailing lists...

...--------------------- The following example shows how we can use StreamExecutor to create a `TypedKernel` instance, associate device code with that instance, and then use that instance to schedule work on an accelerator device. .. code-block:: c++ #include <cassert> #include "stream_executor.h" namespace se = streamexecutor; // A PTX string defining a CUDA kernel. // // This PTX string represents a kernel that takes two arguments: an input value // and an output pointer. The input value is a floating point number. The output // value is a pointer to a flo...

...example shows how we can use StreamExecutor to create a > `TypedKernel` instance, associate device code with that instance, and then > use that instance to schedule work on an accelerator device. > > .. code-block:: c++ > > #include <cassert> > > #include "stream_executor.h" > > namespace se = streamexecutor; > > // A PTX string defining a CUDA kernel. > // > // This PTX string represents a kernel that takes two arguments: an > input value > // and an output pointer. The input value is a floating point number. > Th...

...eamExecutor to create a >> `TypedKernel` instance, associate device code with that instance, and then >> use that instance to schedule work on an accelerator device. >> >> .. code-block:: c++ >> >> #include <cassert> >> >> #include "stream_executor.h" >> >> namespace se = streamexecutor; >> >> // A PTX string defining a CUDA kernel. >> // >> // This PTX string represents a kernel that takes two arguments: an >> input value >> // and an output pointer. The input value is...

...will be a top-level docs directory > for > > the project and a docs directory for each subproject. To begin with, > > StreamExecutor will be the only subproject so the structure will look > > something like this: > > > > parallel-libs/ > > docs/ > > stream_executor/ > > docs/ > > > > Does that seem like a reasonable way to set it up? > > What will it look like when they add the liboffload from OMP? > > Would it be parallel-libs/libomptarget/ > or > parallel-libs/omp/libomptarget/ > > If there's any code in SE...

Hi Tanya, As discussed in the past few weeks in the llvm-dev thread “RFC: Proposing an LLVM subproject for parallelism runtime and support libraries”, we would like to start a new LLVM subproject called parallel-libs (a kind of a parallel cousin to compiler-rt), and I was told you were the one to contact in order to get it created. The charter for the project is included below. Are you able to