Skip to content

Enable strong volatile ordering#9643

Draft
hyunjiki-amd wants to merge 1 commit intoXilinx:masterfrom
hyunjiki-amd:volatile-switch
Draft

Enable strong volatile ordering#9643
hyunjiki-amd wants to merge 1 commit intoXilinx:masterfrom
hyunjiki-amd:volatile-switch

Conversation

@hyunjiki-amd
Copy link
Copy Markdown
Collaborator

Problem solved by the commit

Enable strong volatile ordering

Bug / issue (if any) fixed, which PR introduced the bug, how it was discovered

/volatile:ms switch enables Microsoft extended volatile semantics that guarantee strong ordering

How problem was solved, alternative solutions (if any) and why they were rejected

Could add as AdditionalOptions in vcxproj files

Risks (if any) associated the changes in the commit

None

What has been tested and how, request additional testing if necessary

Confirmed that the compile option is successfully set by building locally

Documentation impact (if any)

None

`/volatile:ms` switch enables Microsoft extended volatile semantics that guarantee strong ordering

Could add as AdditionalOptions in vcxproj files

None

Confirmed that the compile option is successfully set by building
locally

None
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Mar 4, 2026

clang-tidy review says "All clean, LGTM! 👍"

@yanyu-amd
Copy link
Copy Markdown

Hi @hyunjiki-amd

Let's try turn on warning-c4746 to see if we have any compiler volatile switch dependent volatile usage in the code.

https://learn.microsoft.com/en-us/cpp/error-messages/compiler-warnings/compiler-warning-c4746?view=msvc-170

Copy link
Copy Markdown
Collaborator

@stsoe stsoe left a comment

Choose a reason for hiding this comment

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

It's my understand this option is not recommended. Can you explain the reasoning behind adding this option?

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants