8226198: use of & instead of && in LibraryCallKit::arraycopy_restore_alloc_state
Summary: Used logical operator correctly
Reviewed-by: kvn, thartmann
--- a/src/hotspot/share/opto/library_call.cpp Mon Jun 17 17:14:05 2019 -0700
+++ b/src/hotspot/share/opto/library_call.cpp Tue Jun 18 10:00:35 2019 +0530
@@ -4501,8 +4501,8 @@
ciMethod* trap_method = alloc->jvms()->method();
int trap_bci = alloc->jvms()->bci();
- if (!C->too_many_traps(trap_method, trap_bci, Deoptimization::Reason_intrinsic) &
- !C->too_many_traps(trap_method, trap_bci, Deoptimization::Reason_null_check)) {
+ if (!C->too_many_traps(trap_method, trap_bci, Deoptimization::Reason_intrinsic) &&
+ !C->too_many_traps(trap_method, trap_bci, Deoptimization::Reason_null_check)) {
// Make sure there's no store between the allocation and the
// arraycopy otherwise visible side effects could be rexecuted
// in case of deoptimization and cause incorrect execution.