News for hackers. Stuff that matters.

A comment on Finding JIT Optimizer Bugs Using SMT Solvers and Fuzzing – PyPy.

Re:Finding JIT Optimizer Bugs Using SMT Solvers and Fuzzing ... by develatio on Thursday December 15, 2022 @06:03PM (#34007062)
This is very interesting! Were these bugs reported to the Python tracker? Also, what are the actual implications of these bugs in real code? What happens when such a bug is genuinely hit? Are there just performance penalties or are there actual miscalculations in the end result?
[ Parent | on HN ]
Re:Finding JIT Optimizer Bugs Using SMT Solvers and Fuzzing ... by kzrdude on Thursday December 15, 2022 @06:31PM (#34007338)
Note that these are bugs in pypy and not in "Python" i.e not in the dominant python implementation.
[ Parent | on HN ]
Re:Finding JIT Optimizer Bugs Using SMT Solvers and Fuzzing ... by develatio on Thursday December 15, 2022 @06:53PM (#34007558)
Right, thanks for the clarification!
[ Parent | on HN ]
Re:Finding JIT Optimizer Bugs Using SMT Solvers and Fuzzing ... by cfbolztereick on Saturday December 17, 2022 @01:45PM (#34030815)
There would be an actual miscalculation, yes. which is a really annoying kind of bug, also because these jit bugs tend to go away if you turn the debugger on, making them even more frustrating to track down.

The ones we found so far are all extremely unlikely to occur in 'regular' Python code, because they require the use of internal pypy specific numerical operations.

[ Parent | on HN ]