You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, through optimization, sometimes nodes are split into a suboptimal amount of basic blocks, which might reduce the efficiency of subsequent optimizations.
This would actually be "useful" for the backend, as some of our more esoteric crashes stem from unnecessarily split basic blocks (e.g. the problems in #217 with Cmp and Cond being spread over 2 BBs even though they could be in one).
Technically, it shouldn't matter for the backend, though.
Currently, through optimization, sometimes nodes are split into a suboptimal amount of basic blocks, which might reduce the efficiency of subsequent optimizations.
The following is an example:
The ASM for the hand optimized routine is:
The compiler optimized routine has unnecessary basic blocks, resulting in fallthroughs to be visible in the ASM:
The text was updated successfully, but these errors were encountered: