Let's *ping* for Richard.
with the sincos infrastructure in the middle end (I think all patches
are now in the trunk), this speeds up the Polyhedron fatigue test a lot:
~28.3s => ~18.3s (35% faster).
This can be seen at the page
http://www.suse.de/~gcctest/c++bench/polyhedron/polyhedron-summary.txt-fatigue-15.png
of http://www.suse.de/~gcctest/c++bench/polyhedron/
(The patch was applied for one day.)
Tobias
Richard Guenther schrieb:
As $subject says. The cbrt builtins can be used to expand x**1./3. to
cbrt, the other two are on-top of the sincos patches.
Bootstrap / regtest running.
Ok if the sincos patch(es) go in? How can we tell that the target
supports sincos? (I guess we would need a configure check for that?)