@HemanthSai7

TFLM (aka LRTM) welcomes PR contributions! Please submit your PR at your leisure with these rules in mind:

• All code must comply with Google C++ style rules
• All added files (if any) must build through both Makefile and Bazel
• Unit tests that allow complete code coverage must be submitted

So you would need unit tests in sub_test.cc for INT32 that cover both broadcast and non-broadcast (just like the INT16). Also be aware that if this is your first time submitting code, you will need to sign the CLA. You will be presented with information on how to do this when you submit the PR.

Also, somewhere in the PR description there must be a line bug=#xxxx where xxxx is this issue number.

Okay, I will keep these points in mind.

"This issue is being marked as stale due to inactivity. Remove label or comment to prevent closure in 5 days."

This issue is not stale. I will create a PR.

"This issue is being marked as stale due to inactivity. Remove label or comment to prevent closure in 5 days."

"This issue is being closed because it has been marked as
stale for 5 days with no further activity."

How to reopen this issue?