Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/19082
https://github.com/apache/spark/pull/18931 is not what we want, although it
can partially resolves some issues. Simply disabling the whole-stage codegen
might trigger the regression like Q66. The general goal is to maximize the
advantage of both whole-stage codegen and JIT optimization. Now, the point is
how to cut the boundaries without introducing the extra IR.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
