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
{{ message }}
This repository has been archived by the owner on Jan 19, 2024. It is now read-only.
May I kindly ask your preference over GlobalISel and SelectionDAG as the driver of the code generator ?
My understanding is that GlobalISel is expected to eventually replace SelectionDAG, and is easier to work with (both in LOC required to implement code generation, and in testing). What is your opinion, and are there pitfalls that I'm overlooking?
I'm 100% go into GlobalISel since it is more easier to debug and test with.
and are there pitfalls that I'm overlooking?
One of the minor drawbacks when I was working on it in 2021 was the lack of certain pattern matching support from TableGen, which didn't bother since you can write with C++.
Compiling the following program using the command
llc func.ll --global-isel --march=delendum --stop-after=legalizer
:results in a memory exception when
LegalizeRuleSet::getAlias
is called.The text was updated successfully, but these errors were encountered: