-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove merge-files option #1407
base: develop
Are you sure you want to change the base?
Conversation
We still need mergeFiles=False feature when tuning using config yaml in TensileLite. |
Can you explain how it is used in that context? What do you mean by
There are tests that specify |
I am also interested in learning more about how Either way, this update cleans up a lot of (what appears to be) unused code in TensileCreateLibrary. |
MergeFiles=False separates the code object, and makes us easier to modify and compile them individually when we modify the assembly files directly. |
A few more questions
|
I ran the NN problem from
This is the same result for
Note that the primary difference is that with
which we can contrast with
Note that we now have many more hsaco files and four co files rather than one. I don't understand how the difference in these outputs makes it easier to modify an assembly file and compile. Are you using asm-new.sh? Is it easier because you have fewer files that you have to pass to asm-new.sh? It seems to me that you want to be able to incrementally modify and build assembly and maybe merge files isn't the only way to solve that problem. |
In efforts to simplify
TensileCreateLibrary
and recognizing that primary consumers exclusively use merge-files, we are removing the merge-files option along with num-merge-files. If this option is needed in the future, we can restore this behavior but in such a way that we follow the open/closed principle.