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.

Sign up for GitHub

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

Jump to bottom

[Arm64] CQ Evaluate removing half barriers introduced in #14329 #9067

Closed
sdmaclea opened this issue Oct 5, 2017 · 0 comments
Closed

[Arm64] CQ Evaluate removing half barriers introduced in #14329 #9067

sdmaclea opened this issue Oct 5, 2017 · 0 comments
Assignees
@sdmaclea
Labels
arch-arm64 area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI design-discussion Ongoing discussion about design without consensus optimization tenet-performance Performance related issue
Milestone
Future

Comments

@sdmaclea
Copy link
Contributor

sdmaclea commented Oct 5, 2017

dotnet/coreclr#14329 introduces barriers in the exclusive ld/st ops related to atomics. Decide whether these barriers are required for these atomic nodes. Remove if necessary.

// The following instruction includes a acquire half barrier

// The following instruction includes a release half barrier

// The following instruction includes a acquire half barrier

// The following instruction includes a release half barrier
@msftgits msftgits transferred this issue from dotnet/coreclr Jan 31, 2020
@msftgits msftgits added this to the Future milestone Jan 31, 2020
@dotnet dotnet locked as resolved and limited conversation to collaborators Dec 20, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@sdmaclea sdmaclea

Labels
arch-arm64 area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI design-discussion Ongoing discussion about design without consensus optimization tenet-performance Performance related issue
Projects
None yet
Milestone
Future
Development

No branches or pull requests
2 participants
@msftgits @sdmaclea