-
Notifications
You must be signed in to change notification settings - Fork 6.3k
8369190: JavaFrameAnchor on AArch64 has unnecessary barriers and wrong store order in MacroAssembler #27645
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
base: master
Are you sure you want to change the base?
8369190: JavaFrameAnchor on AArch64 has unnecessary barriers and wrong store order in MacroAssembler #27645
Changes from all commits
462c63e
a0058eb
a141449
253417f
016769d
6dd80d9
7dc3313
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -96,4 +96,11 @@ inline int g_isfinite(jdouble f) { return isfinite(f); } | |
#define ALWAYSINLINE inline __attribute__ ((always_inline)) | ||
#define ATTRIBUTE_FLATTEN __attribute__ ((flatten)) | ||
|
||
// Complier barrier which prevents the compiler from reordering loads and stores. | ||
// It does not prevent the hardware from doing so. Typically you should use | ||
// OrderAccess instead. | ||
static inline void compiler_barrier() { | ||
__asm__ volatile ("" : : : "memory"); | ||
} | ||
|
||
Comment on lines
+99
to
+105
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. You can do this in portable C++ since C++11:
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. There are some rules about not calling the Standard C++ libraries in the Guidelines, but given that this one only prevents the compiler from moving things around and does not generate any code, I don't think that really applies. More legalisticaily-minded people might disagree, but I prefer portable code. |
||
#endif // SHARE_UTILITIES_GLOBALDEFINITIONS_GCC_HPP |
Uh oh!
There was an error while loading. Please reload this page.