Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[backport] Remove memory copy in matmul #6241

Merged
merged 3 commits into from Dec 20, 2021
Merged

[backport] Remove memory copy in matmul #6241

merged 3 commits into from Dec 20, 2021

Conversation

toslunar
Copy link
Member

toslunar and others added 3 commits December 15, 2021 15:50
@toslunar
Merge pull request cupy#6179 from okuta/remove-memory-copy
ef9dd8f 
Remove memory copy in matmul
@toslunar
Merge pull request cupy#6195 from toslunar/matmul
dc06deb 
Make `matmul` support ufunc kwargs
@toslunar
Merge pull request cupy#6216 from toslunar/matmul-overlap
66d116b 
Fix overlapping `out` in `matmul` and `(tensor)dot`
@toslunar toslunar added the backport Pull-requests backported from development branch label Dec 15, 2021
@toslunar
Copy link
Member Author

/test mini

@emcastillo emcastillo added this to the v11.0.0a1 milestone Dec 15, 2021
@emcastillo emcastillo merged commit 0c06807 into cupy:v10 Dec 20, 2021
@kmaehashi kmaehashi added the cat:enhancement Improvements to existing features label Dec 20, 2021
@kmaehashi kmaehashi mentioned this pull request Dec 20, 2021
Merged
@toslunar toslunar deleted the bp-6179 branch December 21, 2021 05:25
@toslunar toslunar modified the milestones: v11.0.0a1, v10.1.0 Dec 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@emcastillo emcastillo emcastillo approved these changes

Assignees

@emcastillo emcastillo

Labels
backport Pull-requests backported from development branch cat:enhancement Improvements to existing features
Projects
None yet
Milestone
v10.1.0
Development

Successfully merging this pull request may close these issues.

None yet
3 participants
@toslunar @emcastillo @kmaehashi