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

_controlfp_s: Describe effects of FPCR changes on ARM #5090

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

olologin
Copy link

We believe this note should be somewhere close to _controlfp_s documentation.
More details:
https://stackoverflow.com/questions/78917793/windows-on-arm-math-is-not-trapping

Copy link
Contributor

@olologin : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Copy link
Contributor

Learn Build status updates of commit b0c3732:

✅ Validation status: passed

File Status Preview URL Details
docs/c-runtime-library/reference/controlfp-s.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@Court72
Copy link
Contributor

Court72 commented Aug 27, 2024

@TylerMSFT

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@Court72 Court72 added the aq-pr-triaged Tracking label for the PR review team label Aug 27, 2024
@TylerMSFT
Copy link
Collaborator

Hi, we are looking into this.

@olologin
Copy link
Author

olologin commented Sep 8, 2024

Of course it is better to make it possible to enable exception handling, at least optionally. Because it doesn't look like a good idea to disable them for all ARM CPUs without a way to enable them, just because some ARM CPUs don't support it.

But that is not documentation-related.

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.

3 participants