Dynamically create memory configs #605
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jnie-TT
force-pushed
the
jnie/input_output_memory_config
branch
from
c800a32 to
4522a46
Compare
jnie-TT
force-pushed
the
jnie/input_output_memory_config
branch
8 times, most recently
from
a5ca846 to
0a53313
Compare
nsmithtt
approved these changes
Sep 5, 2024
…RAM_MEMORY_CONFIG, pass output mem config into ops
jnie-TT
force-pushed
the
jnie/input_output_memory_config
branch
from
0a53313 to
294cf2d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
closes #450
Dynamically create memory configs in ToMemoryConfigOp instead of using default L1/DRAM_MEMORY_CONFIG. Derive and pass output memory config into ops accordingly.