Skip to content

Define ET_HAS_EXCEPTIONS macro #11603

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

Merged
merged 2 commits into from
Jun 14, 2025

Conversation

swolchok
Copy link
Contributor

@swolchok swolchok commented Jun 12, 2025

Stack from ghstack (oldest at bottom):

To support passing ET_USE_PYTORCH_HEADERS only when exceptions are enabled.

Differential Revision: D76470039

To support passing ET_USE_PYTORCH_HEADERS only when exceptions are enabled.

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

[ghstack-poisoned]
Copy link

pytorch-bot bot commented Jun 12, 2025

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/11603

Note: Links to docs will display an error until the docs builds have been completed.

✅ You can merge normally! (2 Unrelated Failures)

As of commit f713d4b with merge base d660bde (image):

BROKEN TRUNK - The following jobs failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Jun 12, 2025
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D76470039

@@ -171,6 +171,14 @@
using ssize_t = ptrdiff_t;
#endif

#ifdef __EXCEPTIONS
#define ET_HAS_EXCEPTIONS 1
#elif defined(_HAS_EXCEPTIONS) && _HAS_EXCEPTIONS
Copy link
Contributor

Choose a reason for hiding this comment

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

just curious where do __EXCEPTIONS and _HAS_EXCEPTIONS come from?

Copy link
Contributor

@JacobSzwejbka JacobSzwejbka Jun 13, 2025

Choose a reason for hiding this comment

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

Oh its in the test plan internally. From the compilers.

@swolchok swolchok added the release notes: api Changes to public facing apis (any interfaces, pybinded runtime methods, etc.) label Jun 13, 2025
To support passing ET_USE_PYTORCH_HEADERS only when exceptions are enabled.

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

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

This pull request was exported from Phabricator. Differential Revision: D76470039

@facebook-github-bot facebook-github-bot merged commit 051cb78 into gh/swolchok/456/base Jun 14, 2025
94 of 97 checks passed
@facebook-github-bot facebook-github-bot deleted the gh/swolchok/456/head branch June 14, 2025 00:49
swolchok added a commit that referenced this pull request Jun 14, 2025
Pull Request resolved: #11603

To support passing ET_USE_PYTORCH_HEADERS only when exceptions are enabled.
ghstack-source-id: 290334875
@exported-using-ghexport

Differential Revision: [D76470039](https://our.internmc.facebook.com/intern/diff/D76470039/)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. fb-exported release notes: api Changes to public facing apis (any interfaces, pybinded runtime methods, etc.)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants