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.

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

[ROCm] Add ROCm support for crop_and_resize_op #29150

Conversation

jerryyin
Copy link
Member

@jerryyin jerryyin commented May 29, 2019

This PR adds ROCm support for crop_and_resize_op

The changes in this PR are trivial, please review and merge...thanks.


test preformed: //tensorflow/core/kernels:crop_and_resize_op_test

@tatianashp @whchung

@tensorflow-bot tensorflow-bot bot added the size:M CL Change Size: Medium label May 29, 2019
@jerryyin jerryyin changed the title [ROCm] Add ROCm support for crop and resize op [ROCm] Add ROCm support for crop_and_resize_op May 29, 2019
@rthadur rthadur requested a review from chsigg May 30, 2019 00:41
@rthadur rthadur self-assigned this May 30, 2019
@rthadur rthadur added this to Assigned Reviewer in PR Queue via automation May 30, 2019
@rthadur rthadur added the cuda label May 30, 2019
PR Queue automation moved this from Assigned Reviewer to Approved by Reviewer May 30, 2019
@tensorflow-bot tensorflow-bot bot added kokoro:force-run Tests on submitted change ready to pull PR ready for merge process labels May 30, 2019
@kokoro-team kokoro-team removed the kokoro:force-run Tests on submitted change label May 30, 2019

#if GOOGLE_CUDA
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we should put these lines in a shared place. If it's not too much trouble, and in a separate PR.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I looked around a little bit for this. It looks like ScopedActivateExecutorContext in either cuda::ScopedActivateExecutorContext, or rocm::ScopedActivateExecutorContext, are just alias to gpu::ScopedActivateExecutorContext. Is it easier to just move the corresponding using stream_executor::*::ScopedActivateExecutorContext to either rocm_activation.h or cuda_activation.h?

@tensorflow-bot tensorflow-bot bot added the kokoro:force-run Tests on submitted change label Jun 4, 2019
@kokoro-team kokoro-team removed the kokoro:force-run Tests on submitted change label Jun 4, 2019
@tensorflow-copybara tensorflow-copybara merged commit 3f6d0ea into tensorflow:master Jun 5, 2019
PR Queue automation moved this from Approved by Reviewer to Merged Jun 5, 2019
tensorflow-copybara pushed a commit that referenced this pull request Jun 5, 2019
…r-crop_and_resize_op

PiperOrigin-RevId: 251543853
@jerryyin jerryyin deleted the google-upstream-pr-crop_and_resize_op branch December 20, 2019 17:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: yes ready to pull PR ready for merge process size:M CL Change Size: Medium
Projects
PR Queue
  
Merged
Development

Successfully merging this pull request may close these issues.

None yet

7 participants