Displaying 8 results from an estimated 8 matches for "renderman".
2012 May 09
2
[LLVMdev] Metadata for Argument, BasicBlock
...e to other passes.
The analysis is only one way to supply the necessary information to the
vectorizer - it could also be generated by a front-end directly. This is
a very likely use-case for data-parallel languages that have specific
constructs like "uniform"/"varying" (e.g. RenderMan in graphics).
Metadata is the perfect thing to store this kind of information.
>> I could imagine there are other things that could make use of this, or am I wrong with that?
>
> There are surely many things it could be used for. Interesting
> questions include whether or not there...
2011 Mar 05
0
[LLVMdev] Two languages in the same IR
Hey,
we are intermixing LLVM IR generated from C code with IR generated from
our custom RenderMan frontend. I am not sure whether this is relevant
for you, but in our restricted setting (the C code does not change
frequently and we have full control at link time) this works flawless.
Best,
Ralf
Am 05.03.2011 11:42, schrieb Renato Golin:
> Hi all,
>
> Is it possible to merge two dif...
2012 May 09
0
[LLVMdev] Metadata for Argument, BasicBlock
...her passes.
>
> The analysis is only one way to supply the necessary information to the vectorizer - it could also be generated by a front-end directly. This is a very likely use-case for data-parallel languages that have specific constructs like "uniform"/"varying" (e.g. RenderMan in graphics). Metadata is the perfect thing to store this kind of information.
I'm not a graphics expert, but my understanding of "uniform/varying" is that it's really
a property of values, the values which determine which basic blocks are executed, rather
than of the basic block...
2011 Mar 05
4
[LLVMdev] Two languages in the same IR
Hi all,
Is it possible to merge two different languages in the same IR?
With Java, JNI specifies a whole lot of rules to make C structures and
PCS work with Java classes, if we were to do the same thing in IR,
would that work?
Is there anyone doing this today (with any language)?
--
cheers,
--renato
http://systemcall.org/
Reclaim your digital rights, eliminate DRM, learn more at
2012 May 09
1
[LLVMdev] Metadata for Argument, BasicBlock
...ses.
>>
>> The analysis is only one way to supply the necessary information to the vectorizer - it could also be generated by a front-end directly. This is a very likely use-case for data-parallel languages that have specific constructs like "uniform"/"varying" (e.g. RenderMan in graphics). Metadata is the perfect thing to store this kind of information.
>
> I'm not a graphics expert, but my understanding of "uniform/varying" is that it's really
> a property of values, the values which determine which basic blocks are executed, rather
> than...
2007 Dec 15
1
[LLVMdev] llvm and assemble code
Hi Guys,
I am really a fresh man on compiler. I want to make a compiler that transform C-like language into assemble form, as the the same as Pixie's or Aqsis's RenderMan Shading Language compiler, just like this,
#!version 2.1.1
surface
#!parameters:
uniform float Ka = 1
uniform float Kd = 1
#!variables:
varying vector Nf
varying vector temporary_0
varying vector temporary_1
varying vector temporary_2
uniform vector temporary_3
varying vector temporary_4
varying v...
2012 May 09
0
[LLVMdev] Metadata for Argument, BasicBlock
On May 7, 2012, at 11:11 PM, Ralf Karrenberg <Chareos at gmx.de> wrote:
> Hi Dan,
>
> I am using it to store results of a vectorization analysis. A BasicBlock has certain properties in this context, e.g. we mark control flow that may never diverge in different instances ("threads" if you think in terms of CUDA) of the same function by marking the corresponding blocks.
2012 May 08
2
[LLVMdev] Metadata for Argument, BasicBlock
Hi Dan,
I am using it to store results of a vectorization analysis. A BasicBlock
has certain properties in this context, e.g. we mark control flow that
may never diverge in different instances ("threads" if you think in
terms of CUDA) of the same function by marking the corresponding blocks.
This information is later used when linearizing the function (control
flow to data flow