Skip to content

add support for type_as/_to_copy#77971

Closed
eellison wants to merge 15 commits intogh/eellison/294/basefrom
gh/eellison/294/head
Closed

add support for type_as/_to_copy#77971
eellison wants to merge 15 commits intogh/eellison/294/basefrom
gh/eellison/294/head

Conversation

[ghstack-poisoned]
@facebook-github-bot
Copy link
Contributor

facebook-github-bot commented May 20, 2022

🔗 Helpful links

✅ No Failures (0 Pending)

As of commit 88a6bc9 (more details on the Dr. CI page):

Expand to see more

💚 💚 Looks good so far! There are no failures yet. 💚 💚


This comment was automatically generated by Dr. CI (expand for details).

Please report bugs/suggestions to the (internal) Dr. CI Users group.

Click here to manually regenerate this comment.

Without this I would get strange `invalid arguments` in CUDA call.

[ghstack-poisoned]
@eellison eellison requested review from Chillee and ezyang May 20, 2022 16:17
Elias Ellison added 3 commits May 20, 2022 11:23
Without this I would get strange `invalid arguments` in CUDA call.

[ghstack-poisoned]
Without this I would get strange `invalid arguments` in CUDA call.

[ghstack-poisoned]
Without this I would get strange `invalid arguments` in CUDA call.

[ghstack-poisoned]
# Run the original computation

# _to_copy fails when run with FakeTensors to cuda device
# TODO: debug
Copy link
Contributor

Choose a reason for hiding this comment

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

You're talking about the meta implementation here right? It makes sense, since we can't actually produce the cuda data (but for fake tensor that's OK, because the fake cuda device doesn't have data anyway)

Elias Ellison added 4 commits May 23, 2022 13:28
Without this I would get strange `invalid arguments` in CUDA call.

[ghstack-poisoned]
Without this I would get strange `invalid arguments` in CUDA call.

[ghstack-poisoned]
Without this I would get strange `invalid arguments` in CUDA call.

[ghstack-poisoned]
Without this I would get strange `invalid arguments` in CUDA call.

[ghstack-poisoned]
@eellison
Copy link
Contributor Author

@eellison has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

Without this I would get strange `invalid arguments` in CUDA call.

Differential Revision: [D36618463](https://our.internmc.facebook.com/intern/diff/D36618463)

[ghstack-poisoned]
@eellison
Copy link
Contributor Author

@eellison has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

Elias Ellison added 3 commits May 24, 2022 15:59
Without this I would get strange `invalid arguments` in CUDA call.

Differential Revision: [D36618463](https://our.internmc.facebook.com/intern/diff/D36618463)

[ghstack-poisoned]
Without this I would get strange `invalid arguments` in CUDA call.

Differential Revision: [D36618463](https://our.internmc.facebook.com/intern/diff/D36618463)

[ghstack-poisoned]
Without this I would get strange `invalid arguments` in CUDA call.

Differential Revision: [D36618463](https://our.internmc.facebook.com/intern/diff/D36618463)

[ghstack-poisoned]
Without this I would get strange `invalid arguments` in CUDA call.

Differential Revision: [D36618463](https://our.internmc.facebook.com/intern/diff/D36618463)

[ghstack-poisoned]
Without this I would get strange `invalid arguments` in CUDA call.



[ghstack-poisoned]
@eellison eellison mentioned this pull request May 31, 2022
@eellison
Copy link
Contributor Author

@pytorchbot merge this please

@github-actions
Copy link
Contributor

Hey @eellison.
You've committed this PR, but it does not have both a 'release notes: ...' and 'topics: ...' label. Please add one of each to the PR. The 'release notes: ...' label should represent the part of PyTorch that this PR changes (fx, autograd, distributed, etc) and the 'topics: ...' label should represent the kind of PR it is (not user facing, new feature, bug fix, perf improvement, etc). The list of valid labels can be found here for the 'release notes: ...' and here for the 'topics: ...'.
For changes that are 'topic: not user facing' there is no need for a release notes label.

facebook-github-bot pushed a commit that referenced this pull request Jun 1, 2022
Summary:
Pull Request resolved: #77971

Approved by: https://github.com/ezyang

Test Plan: contbuild & OSS CI, see https://hud.pytorch.org/commit/pytorch/pytorch/4c18f362a9d88e664fa1ced1ac77e1c6ccac960e

Reviewed By: seemethere

Differential Revision: D36784772

Pulled By: seemethere

fbshipit-source-id: 76e3be49c6a723ed7094436adf89a01df065c909
@facebook-github-bot facebook-github-bot deleted the gh/eellison/294/head branch June 4, 2022 14:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants