Search found 3 matches

by illwieckz
Wed Jun 15, 2022 11:00 pm
Forum: Development
Topic: Looking for help to identify a compiler bug in Clang uncovered by LuxMark/LuxCore
Replies: 3
Views: 898

Re: Looking for help to identify a compiler bug in Clang uncovered by LuxMark/LuxCore

I'm still able to reproduce the bug when I reduce the luxball/scene.scn scene file to this: scene.camera.lookat.orig = 0.649246990680694580078125 0.279195994138717651367188 0.148695006966590881347656 scene.camera.lookat.target =0.107509911060333251953125 1.0487911701202392578125 -0.18930505216121673...
by illwieckz
Thu May 26, 2022 5:01 pm
Forum: Development
Topic: Looking for help to identify a compiler bug in Clang uncovered by LuxMark/LuxCore
Replies: 3
Views: 898

Re: Looking for help to identify a compiler bug in Clang uncovered by LuxMark/LuxCore

Thank you for your answer. I was afraid investigating this from LuxMark side would not be easy, you seems to confirm it. One interesting thing I noticed in the mean time is that PoCL pthread (CPU implementation) that is also relying heavily on LLVM suffered from a very similar problem in LLVM 11, me...
by illwieckz
Wed May 18, 2022 12:08 am
Forum: Development
Topic: Looking for help to identify a compiler bug in Clang uncovered by LuxMark/LuxCore
Replies: 3
Views: 898

Looking for help to identify a compiler bug in Clang uncovered by LuxMark/LuxCore

Hi, I found a bug in the `-ffast-math` option of the LLVM Clang compiler that is reproduced when compiling OpenCL code using LuxMark. I'm looking for help to narrow the reproduction test with hope to get this Clang bug fixed. Some context: The Mesa Clover radeonsi OpenCL driver for AMD GCN and later...