We are consolidating OPs in TTNN

[ayerofieiev-tt]

👋 Hi everyone! Here is an update on one of our ongoing TTNN efforts.

Background

Today Operations are split between tt_dnn and ttnn. Many ops in ttnn call their tt_dnn implementation. Some ops like unary and binary duplicate code leading to 2 different pathways in C++ / Python. This not only confuses new contributors, but increases time required to make changes. For example, as we add support for queue_id and output_tensor - we have to add them to ops in both libs.
So we are now merging the two, moving code from tt_dnn to ttnn, removing tt_lib and consolidating OPs in a single place.
See details in #9322.

Tracking the work here: https://github.com/orgs/tenstorrent/projects/30/views/7 (currently accounts for ~60% of the scope)

We are now in Phase 3: Mass migrating ops. Very excited to see how more and more operations are consolidated in a single place! Lots of folks are involved to make this happen! 🙌

I believe this work provides a strong foundation for the rest of the preparation before the TTNN v1.0 release!

How does this affect you?

We expect minimal-to-no impact:

• If your PR is failing due to a missing tt_lib binding, just switch to ttnn op;
• If you add a new op, add it directly to ttnn and export in ttnn module as experimental;
• If you have a model/example which is not running as a part of main CI workflows - you can expect them break 🤷

Let us know if you have any questions!

[ayerofieiev-tt]

🚀 Update!

We are excited to announce the successful merge of a significant change (#9870).
Moving forward, all tt-eager sources will be built as part of ttnn, resulting in the removal of tt-eager.so.
All functionality is now consolidated within ttnn.so.

While the tt-eager folder remains, it has been symlinked inside ttnn as a temporary measure.

Why the Symlink?

We are currently undertaking a massive effort to integrate operations into ttnn, as detailed in our project tracker. The symlink is a temporary solution to avoid disrupting this ongoing process. We will remove the symlink once the rate of changes to tt-eager and ttnn stabilizes.

How Does This Affect You?

Please refrain from adding new operations to tt_dnn. Instead, direct all new operations to ttnn following this guide.

Next Steps

In the coming weeks, we will focus on:

• Remove the symlink and physically integrating all tt-eager files into ttnn.
• Reorganize files into their appropriate locations (e.g., operation.hpp, run_operation.hpp, queue, tensor, etc.).
• Eliminate all usage of tt_lib.* across the repository and remove the tt_lib Python library from within ttnn.

A big thank you to @tt-rkim, @eyonland, and @arakhmati for their help!

[ayerofieiev-tt]

🚀 Update!

Contents of tt_eager folder is now moved to ttnn/cpp/ttnn/deprecated. Symlink is removed.
#10424

Going forward new NN operations should be added to ttnn/operations/.