-
Notifications
You must be signed in to change notification settings - Fork 739
[STABLE ABI] Port forced_align #4079
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
Open
pearu
wants to merge
5
commits into
pytorch:main
Choose a base branch
from
pearu:pearu/stable-abi-forced_align
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
ed1d81d
[STABLE ABI] Port forced_align
pearu c4478d2
Collect a torch::stable wishlist in src/libtorchaudio/stable
pearu e246029
Collect a torch::stable wishlist in src/libtorchaudio/stable
pearu bbf6f38
Apply pre-commit
pearu b308882
Add toString(ScalarType)
pearu File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On the above, can you help me understand why we need to use
STABLE_DISPATCH_INDEX_TYPESnow? Basically, which part ofat::max(inputLengths).item().toInt()do we need to work-around? Is this a permanent workaround, or something we'll be able to simplify in the future when more APIs are ported to the stable part?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Currently,
targetLengthscan be a tensor with int32 or int64 items. If one uses, say,torchaudio::util::max<int32_t>(targetLengths)when targetLengths dtype is int64, the result ofmaxmay be wrong. The usage of STABLE_DISPATCH_INDEX_TYPES makes callingmaxsafe.We can simplify this in future after we are able to rewrite
at::max(inputLengths).item().toInt()using stable ABI methods.