-
Notifications
You must be signed in to change notification settings - Fork 737
Introduce missing APIs to lower ExportedProgram objects directly #8909
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
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/8909
Note: Links to docs will display an error until the docs builds have been completed. ❌ 1 Cancelled JobAs of commit 68a9d95 with merge base 2aa7748 ( CANCELLED JOB - The following job was cancelled. Please retry:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
This pull request was exported from Phabricator. Differential Revision: D70529392 |
|
This pull request was exported from Phabricator. Differential Revision: D70529392 |
ff37f33 to
c8e543d
Compare
Summary: Currently, there is an imbalance in compilation APIs where the `export_to_executorch` function is used on a module, although that module is already from an exported program. This diff introduces APIs to further lower ExportedPrograms directly, without going back to module. Differential Revision: D70529392
c8e543d to
80754c1
Compare
|
This pull request was exported from Phabricator. Differential Revision: D70529392 |
Summary: Pull Request resolved: #8909 Currently, there is an imbalance in compilation APIs where the `export_to_executorch` function is used on a module, although that module is already from an exported program. This diff introduces APIs to further lower ExportedPrograms directly, without going back to module. Differential Revision: D70529392
80754c1 to
b55a6ef
Compare
Summary: Currently, there is an imbalance in compilation APIs where the `export_to_executorch` function is used on a module, although that module is already from an exported program. This diff introduces APIs to further lower ExportedPrograms directly, without going back to module. Differential Revision: D70529392
b55a6ef to
2d0633a
Compare
|
This pull request was exported from Phabricator. Differential Revision: D70529392 |
Summary: Pull Request resolved: #8909 Currently, there is an imbalance in compilation APIs where the `export_to_executorch` function is used on a module, although that module is already from an exported program. This diff introduces APIs to further lower ExportedPrograms directly, without going back to module. Differential Revision: D70529392
2d0633a to
b63347f
Compare
Summary: Currently, there is an imbalance in compilation APIs where the `export_to_executorch` function is used on a module, although that module is already from an exported program. This diff introduces APIs to further lower ExportedPrograms directly, without going back to module. Differential Revision: D70529392
b63347f to
6461ce3
Compare
|
This pull request was exported from Phabricator. Differential Revision: D70529392 |
Summary: Pull Request resolved: #8909 Currently, there is an imbalance in compilation APIs where the `export_to_executorch` function is used on a module, although that module is already from an exported program. This diff introduces APIs to further lower ExportedPrograms directly, without going back to module. Differential Revision: D70529392
6461ce3 to
3dad7d7
Compare
Summary: Currently, there is an imbalance in compilation APIs where the `export_to_executorch` function is used on a module, although that module is already from an exported program. This diff introduces APIs to further lower ExportedPrograms directly, without going back to module. Reviewed By: zonglinpeng Differential Revision: D70529392
3dad7d7 to
2f9cb93
Compare
Summary: Currently, there is an imbalance in compilation APIs where the `export_to_executorch` function is used on a module, although that module is already from an exported program. This diff introduces APIs to further lower ExportedPrograms directly, without going back to module. Reviewed By: zonglinpeng Differential Revision: D70529392
2f9cb93 to
483968d
Compare
|
This pull request was exported from Phabricator. Differential Revision: D70529392 |
Summary: Pull Request resolved: #8909 Currently, there is an imbalance in compilation APIs where the `export_to_executorch` function is used on a module, although that module is already from an exported program. This diff introduces APIs to further lower ExportedPrograms directly, without going back to module. Reviewed By: zonglinpeng Differential Revision: D70529392
483968d to
2889983
Compare
Summary: Pull Request resolved: #8909 Currently, there is an imbalance in compilation APIs where the `export_to_executorch` function is used on a module, although that module is already from an exported program. This diff introduces APIs to further lower ExportedPrograms directly, without going back to module. Reviewed By: zonglinpeng Differential Revision: D70529392
|
This pull request was exported from Phabricator. Differential Revision: D70529392 |
2889983 to
68a9d95
Compare
Differential Revision: D70529392 Pull Request resolved: #8909
Summary: Currently, there is an imbalance in compilation APIs where the
export_to_executorchfunction is used on a module, although that module is already from an exported program. This diff introduces APIs to further lower ExportedPrograms directly, without going back to module.Differential Revision: D70529392