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

Remove call to VMJ9 traceAssumeFailure #3613

Merged
merged 1 commit into from
Feb 26, 2019

Conversation

rwy7
Copy link
Contributor

@rwy7 rwy7 commented Feb 26, 2019

In J9, traceAssumeFailure has been disabled, so calling it has no
effect. This is the only call site, so once it is removed,
traceAssumeFailure can be removed from the J9 VM.

Signed-off-by: Robert Young rwy0717@gmail.com

In J9, traceAssumeFailure has been disabled, so calling it has no
effect. This is the only call site, so once it is removed,
traceAssumeFailure can be removed from the J9 VM.

Signed-off-by: Robert Young <rwy0717@gmail.com>
@0xdaryl
Copy link
Contributor

0xdaryl commented Feb 26, 2019

@genie-omr build all

@0xdaryl
Copy link
Contributor

0xdaryl commented Feb 26, 2019

zOS failure is infrastructural. LoZ tests pass. Merging.

@0xdaryl 0xdaryl merged commit e0b9757 into eclipse-omr:master Feb 26, 2019
@rwy7 rwy7 deleted the remove-j9-trace-assert branch February 27, 2019 01:33
rwy7 added a commit to rwy7/openj9 that referenced this pull request Apr 16, 2019
This function is disabled, and has no callsites in J9. In OMR, there is
one remaining call inside the implemention of TR_ASSERT. Once this call
is removed in eclipse-omr/omr#3613, this function can be deleted.

Signed-off-by: Robert Young <rwy0717@gmail.com>
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.

2 participants