On 23. 11. 22 9:12, Petr Viktorin wrote:
On 22. 11. 22 18:30, Miro Hrončok wrote:
On 21. 11. 22 11:01, Petr Viktorin wrote:
And since the Python slowdown comes from a single weird function, I think
that Fedora should ignore the Python benchmarks when evaluating the distro
default -- and if
On 22. 11. 22 18:30, Miro Hrončok wrote:
On 21. 11. 22 11:01, Petr Viktorin wrote:
And since the Python slowdown comes from a single weird function, I
think that Fedora should ignore the Python benchmarks when evaluating
the distro default -- and if Fedora switches to no-omit-frame-pointer,
On 21. 11. 22 11:01, Petr Viktorin wrote:
And since the Python slowdown comes from a single weird function, I think that
Fedora should ignore the Python benchmarks when evaluating the distro default
-- and if Fedora switches to no-omit-frame-pointer, Python 3.11 should be an
exception (to be
On 09. 11. 22 12:37, Petr Viktorin wrote:
tl;dr: Python 3.12 should be built with no-omit-frame-pointer if
upstream recommends it.
Hello,
You might be aware of a Fedora change proposal [0] (discussed on
fedora-devel [1] and FESCo [2]) are discussing turning on C compiler
flags that help
On 15. 11. 22 20:17, Kevin Kofler wrote:
tl;dr: Python 3.12 should be built with no-omit-frame-pointer if
upstream recommends it.
Absolutely not, because…
Apparently there are some benchmarks that make Python look extra slow
when the flags are turned on
… considering those benchmarks,
> tl;dr: Python 3.12 should be built with no-omit-frame-pointer if
> upstream recommends it.
Absolutely not, because…
> Apparently there are some benchmarks that make Python look extra slow
> when the flags are turned on
… considering those benchmarks, Python is one of the programs for which
tl;dr: Python 3.12 should be built with no-omit-frame-pointer if
upstream recommends it.
Hello,
You might be aware of a Fedora change proposal [0] (discussed on
fedora-devel [1] and FESCo [2]) are discussing turning on C compiler
flags that help with performance *measurement*, but might hurt
