-
Notifications
You must be signed in to change notification settings - Fork 149
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
8186787: clang-4.0 SIGSEGV in Unsafe_PutByte #553
base: master
Are you sure you want to change the base?
Conversation
👋 Welcome back zzambers! A progress list of the required criteria for merging this PR into |
❗ This change is not yet ready to be integrated. |
This backport pull request has now been updated with issue from the original commit. |
Log from failing (segfaulting) tests (without fix, for reference): |
@zzambers This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration! |
keep open |
@zzambers This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration! |
3 similar comments
@zzambers This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration! |
@zzambers This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration! |
@zzambers This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration! |
This backport fixes failures (segfaults) in following tests which appeared after macos update:
Backport differs from original changeset, because there were significant changes/refactoring in unsafe.
Notes:
addr
(MemoryAccess
class), to volatile. Otherwise it is basically just refactoring.MemoryAccess
is used byUnsafe_{Set,Put}*
andUnsafe_{Set,Put}*Volatile
functions, defined usingDEFINE_GETSETOOP
andDEFINE_GETSETOOP_VOLATILE
macrosMemoryAccess
class, so equivalent pointers, in functions mentioned higher, are cast to volatile, to achieve same effectTesting:
Tier1: OK (fixes
sun/misc/CopyMemory.java
andcompiler/unsafe/OpaqueAccesses.java
tests on macos, 1 failure on Linux x86 is timeout - seems unrelated, macos failures explained here: #544 (comment))Progress
Issue
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk8u-dev.git pull/553/head:pull/553
$ git checkout pull/553
Update a local copy of the PR:
$ git checkout pull/553
$ git pull https://git.openjdk.org/jdk8u-dev.git pull/553/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 553
View PR using the GUI difftool:
$ git pr show -t 553
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk8u-dev/pull/553.diff
Webrev
Link to Webrev Comment