This is a very first step to 1. separate the AIE1 and AIE-ML/AIE2 and 2. add support of AIE2P to AIEVEC. Changing from AIE-ML to AIE2 aligns to the target naming convention in AIE/AIEX dialects and passes.
Changes:
Add AIE2P in the AIEVEC pipeline enum.
Rename aieml/aie_ml/aie-ml to aie2 in the AIEVEC related passes and ops in the dialect.
Keep the support of both -convert-vector-to-aievec="aie-target=aieml" and -convert-vector-to-aievec="aie-target=aie2" for compatibility.
Todo:
Update aie-ml to aie2 in lib/Targets/AIEVecToCpp/TranslateRegistration.cpp and update other corresponding python e2e tests.
Update aievec unit tests and integration tests to use aie-target=aie2
This is a very first step to 1. separate the AIE1 and AIE-ML/AIE2 and 2. add support of AIE2P to AIEVEC. Changing from
AIE-MLtoAIE2aligns to the target naming convention inAIE/AIEXdialects and passes.Changes:
AIE2Pin the AIEVEC pipeline enum.aieml/aie_ml/aie-mltoaie2in the AIEVEC related passes and ops in the dialect.-convert-vector-to-aievec="aie-target=aieml"and-convert-vector-to-aievec="aie-target=aie2"for compatibility.Todo:
aie-mltoaie2inlib/Targets/AIEVecToCpp/TranslateRegistration.cppand update other corresponding python e2e tests.aie-target=aie2