I just had a look on the nvcc compiler options we use to compile cuda binaries. First of all we still use --opencc-options that are ignored by nvcc 5.0 and 5.5 when compiling for sm_20 and up. Maybe we should see if there are nvcc optimization options we can use to regain speed when using Cuda 5.0+.
/Jürgen Am 03. Juni 2013 um 11:39 schrieb Jürgen Herrmann <shadow...@me.com>: > Hmm, unfortunately it's the only clean solution for vs 2012 :( > The other solution is to trick nvcc by either using the vc9 platform toolkit > to compile cycles cuda kernel or to manually edit some files to force > compilation with vs 2012. > Both gave me random crashes I could not reproduce with 100% reliability. > > /Jürgen > > Am 03.06.2013 um 11:12 schrieb Thomas Dinges <blen...@dingto.org>: > > > Hi, > > I tested the 5.5 Toolkit already, and unfortunately it still gives a big > > slowdown for Cycles rendering. So updating to 5.5 is not a solution for > > our official releases. :( > > > > Thomas > > > > Am 03.06.2013 10:54, schrieb Jürgen Herrmann: > >> Hi there, > >> > >> I just saw that NVidia has released the Cuda 5.5 RC for registered Cuda > >> devs. > >> It supports VS 2012 now... > >> So I can begin testing with cuda binaries compiled with VS2012 without > >> having to cheat ;) > >> > >> /Jürgen > >> _______________________________________________ > >> Bf-committers mailing list > >> Bf-committers@blender.org > >> http://lists.blender.org/mailman/listinfo/bf-committers > > > > > > -- > > Thomas Dinges > > Blender Developer, Artist and Musician > > > > www.dingto.org > > > > _______________________________________________ > > Bf-committers mailing list > > Bf-committers@blender.org > > http://lists.blender.org/mailman/listinfo/bf-committers _______________________________________________ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
