When will aimet support pytorch2.x

[buxianggaimingzi]

Is there any plan or time for support pytorch2.x? Thank you very much.

[escorciav]

Isn't the pytorch.compile the go to way in 2.x?
If so, it might imply a big departure wrt to torch.fx.

My bet: AIMET might be deprecated or get its scope reduced in 3-5 years

[quic-mangal]

@buxianggaimingzi, we are currently working on supporting PT2.x. Will keep you posted regarding the update.

[escorciav]

Good to know.
Cheering up for the team 💪

Looking fwd to hearing more news.
Especially related to Executorch.

[escorciav]

@buxianggaimingzi out of curiosity, did you try building/compiling AIMET for PyTorch >= 2.0?
@quic-mangal kindly let us know if building/compilation is a dead end with PyTorch 2.0 or above

[quic-mangal]

@escorciav, currently we are still working on the upgrade. Hopefully it should be available by EOM.

[escorciav]

@quic-mangal I understood that. However, I was wondering if I can still build AIMET from source with PyTorch >= 2.1.

A friend did it (fork). However, I'm unable to reproduce his recipe. I'll open another issue to not derail the convo :)

[escorciav]

ping AIMET:maintainers/contributors/users

My friend's fork is a bit outdated. I have to update the model prep again.

Venting. I wish Executorch finally levels up PyTorch on-device & at-the-edge. Thus, AIMET scope (for PyTorch users) gets reduced to (1) kernel delegates (plugins) & recipes, + (2) legacy tool. The latter is mostly for Qualcomm folks. You know as Tensorflow brought up Theano early retirement. I often feel as 👇