Not sure, but I'll try to figure it out after I commit the change that seems to fix things. -- Larry Gritz l...@...

You can find docs for it here: http://llvm.org/docs/Bugpoint.html It seems like this needs to become part of the tool chain so that we can isolate the LLVM problems, get a reduced test case, and get t

Hi, I would like to add OSL to our GPU renderer, but I have no idea on "how to write" a backend. Do you have an example or some instructions to help me to start ? I will start tomorrow morning, I hope

I just posted this to the LLVM mail list, but will repeat here in case anybody lurking happens to know the answers... I think I just discovered the hard way that I can't keep adding to a single Module

It sounds that several peoples are trying to compile under windows, either with Visual studio or with command line. So, maybe it will be interesting to add a VS2008 solution or to create another proje

Reviewers: dev-osl_imageworks.com, osl-dev_googlegroups.com, Description: Avoids printing stats when OSL didn't load any shaders. Avoids a few divisions by 0. Please review this at http://codereview.a

Reviewers: , Description: For two weeks, I've been agonizing over LLVM-related bugs wherein the generated code crashes, and I finally have a fix. Ultimately, it came down to the fact that I was using

Reviewers: , Description: Some more things I noticed during debugging, just cleaning up: some new assertions; things that should probably always have been declared 'inline' but were not; typos; clarif

Reviewers: osl-dev_googlegroups.com, dev-osl_imageworks.com, Description: Add a method that measures how big a closure is. Useful to track the amount of memory taken up by pools of closures on the ren

Reviewers: , Description: More fiddling with optimization passes brings big performance increase. I'm back now to separate function & module pass management. The breakdown is: llvm-gcc does substantia

I grep'd the source and didn't see any actual usage...

Reviewers: , Description: Move more functions from llvm_ops.cpp (llvm compiled) into static compilation and just call those functions from llvm-generated code. This round, we're talking about the prin

I have some code towards adding Ptex support to OSL that I'm getting ready to finish and submit for inclusion. Before I do, I wanted to verify that I'm the only one working on this. Thanks! Best, Eric

Reviewers: , Description: Pass tweaking. Speeds up a bit more. All tests still pass. Please review this at http://codereview.appspot.com/1994043/ Affected files: src/liboslexec/llvm_instance.cpp Index

Reviewers: , Description: After JITing, delete the IR for the shader layers. I did this to save memory (it does), but it also sped up my renders substantially. Of course it does -- we aren't optimizin

Reviewers: dev-osl_imageworks.com, osl-dev_googlegroups.com, Description: This seems to interact incorrectly with applications that define their own signal handlers. Please review this at http://coder

Reviewers: , Description: 1. Add texture() and get_texture_info() callbacks to the RendererServices. The default implementation simply call OIIO textures routines as usual. But a rendering system can

Wow, a much appreciated update! perhaps your renderer can then intercept the texture calls on the way to OIIO and, for those rays that are so blurred out that their quality matters little, adjust the

Sorry for the email review, codereview.appspot.com seems to be down today. I noticed in yesterday's texture overhaul that the way we deal with optional "blur" and "width" arguments to texture() are pr

The developer meeting for LLVM this year is Nov 4. They're taking speaker applications here: http://llvm.org/devmtg/talk.php Is anyone on the OSL team interested in speaking? I'm certain the group wou