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
Mark made some good points: we need to design the code generator as a compiler. I'm not quite sure what the IL (or ILs) should look like. After GH-99526 and GH-99495 have landed I will start thinking about this for real, probably while converting some more families to the non-legacy format. (Doing the conversions is very helpful in forming the right ideas.)
The text was updated successfully, but these errors were encountered:
Actually, I misunderstood Mark's comment. The key part is that we have a standard way to read instruction definitions, and we do, in Tools/cases_generator, in the form of the Analyzer class in generate_cases.py. Things could be factored out slightly better, but the basic framework is there and we'll refactor as needed. So I'm going to close this as "done" (or close enough).
Mark made some good points: we need to design the code generator as a compiler. I'm not quite sure what the IL (or ILs) should look like. After GH-99526 and GH-99495 have landed I will start thinking about this for real, probably while converting some more families to the non-legacy format. (Doing the conversions is very helpful in forming the right ideas.)
The text was updated successfully, but these errors were encountered: