wfpokorny

See my latest comment to pull #358 for more detail. In short for v3.8 do nothing. Merge Jerome's pull request for v4.0.

Don't know myself. There was some recent discussion - past few months - about re-starting development with a focus on 3.7 feature support, but I've not heard anything since. It...

Running povray v3.8 beta 1 which uses Simple DirectMedia Layer 1.2 I can duplicate this issue. Running versions of povray updated to use Simple DirectMedia Layer 2.0, we run cleanly...

Not sure what you mean by your question? I ran 3.7.0 and 3.6.1 just now and the same artifacts appear - supposing you were asking whether this example has issues...

FYI. I now have a branch which fixes this issue at: https://github.com/wfpokorny/povray/tree/fix/polynomialsolverAccuracy I have still to run down some unrelated solver accuracy issues so I'm not creating a pull request...

Thanks for taking a look. I'd not of thought to use valgrind - and I admit too, to not being sure I'm following all the track.txt output. Some thoughts pop...

Stopping for the day, but a major slowdown happened between commits e16458c3 and 3f56c5fb. Using statically linked generic architecture -O3 compiled modules, we were running -6% faster than v3.7 stable...

Rushed info as I'll soon be away until next week. I was able to use the existing O3 generic arch static modules above with the perf tool to see enough...

@LeForgeron, I've explored more here and my thoughts currently more or less echoing your last paragraph. The commit 725efe1f is certainly involved. My leading suspect there is POV_MALLOC and POV_FREE...

An update. **The bad news.** For users getting pre-compiled versions of POV-Ray where the compile target is generic, the v37 to v38 performance penalty is 30-40% or roughly double the...