Support vector-units w/o L1D$ access #3537
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
sequencer
added a commit
to chipsalliance/t1
that referenced
this pull request
Nov 23, 2023
jerryz123
requested changes
Nov 23, 2023
Added |
jerryz123
approved these changes
Nov 25, 2023
|
We should purge these uArch parameters dependencies eventually. But not now;p |
|
@Mergifyio copy master |
✅ Pull request copies have been created
|
|
@Mergifyio copy master |
✅ Pull request copies have been created
|
Avimitin
pushed a commit
to chipsalliance/t1
that referenced
this pull request
Dec 5, 2023
Avimitin
pushed a commit
to chipsalliance/t1
that referenced
this pull request
Dec 5, 2023
Avimitin
pushed a commit
to chipsalliance/t1
that referenced
this pull request
Dec 12, 2023
jerryz123
added a commit
that referenced
this pull request
Jan 4, 2024
Support vector-units w/o L1D$ access (copy #3537)
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.
Without upstreaming these patches, T1 cannot elaborate... We need decouple in the future. Since there is no current valid useVector implementations, I think this is safe to merge.
Related issue:
Type of change: bug report | feature request | other enhancement
Impact: no functional change | API addition (no impact on existing code) | API modification
Development Phase: proposal | implementation
Release Notes