Skip to content

Conversation

@optima2005
Copy link
Contributor

This is a fix to #4604, to remove unnecessary and incorrect cuda schedule for conv3d_ndhwc

@masahi @icemelon9

@tqchen tqchen added status: need test case need test cases to cover the change status: need review labels Jan 8, 2020
@masahi
Copy link
Member

masahi commented Jan 9, 2020

if you remove schedule_conv3d_ndhwc_cuda, what happens if schedule_conv3d_ndhwc was called on cuda target? You get an error?

@icemelon
Copy link
Member

icemelon commented Jan 9, 2020

Never mind. I'll fix the conv3d issue in #4644 since I'm changing the TOPI.

@icemelon icemelon closed this Jan 9, 2020
@optima2005
Copy link
Contributor Author

@masahi Yes. it would report error. Currently at least in TF frontend, the NHWC for conv2d, NDHWC for conv3d are forced to transform to NCHW/NCDHW layout. Please see this, this and this. I guess that might be under perormance consideration. But a more user friendly approach may be needed to notice the user TVM not supporting those layouts under cuda target.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

status: need review status: need test case need test cases to cover the change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants