diff options
| author | 2025-02-17 14:18:17 +0000 | |
|---|---|---|
| committer | 2025-02-18 00:43:56 -0800 | |
| commit | b03ab575b9acb3fd73861d5d0a7719dcd0a6322a (patch) | |
| tree | d7bcaa6e6c247d24e82e5c7e0456e9c82bc5f1b7 /compiler/optimizing | |
| parent | 143d99f3efa04935a3b290e66274178ed38519b1 (diff) | |
Only locking error and runtime throws should retrigger verification.
This ensures the stability of the vdex file.
Test: 412-new-array
Change-Id: I73a6be0a46b6eb184ea127de720bfaf7104f3777
Diffstat (limited to 'compiler/optimizing')
| -rw-r--r-- | compiler/optimizing/instruction_builder.cc | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/compiler/optimizing/instruction_builder.cc b/compiler/optimizing/instruction_builder.cc index 74880463c3..8cc79c2424 100644 --- a/compiler/optimizing/instruction_builder.cc +++ b/compiler/optimizing/instruction_builder.cc @@ -2554,8 +2554,6 @@ bool HInstructionBuilder::BuildFilledNewArray(uint32_t dex_pc, char primitive = descriptor[1]; if (primitive != 'I' && primitive != 'L' && primitive != '[') { DCHECK(primitive != 'J' && primitive != 'D'); // Rejected by the verifier. - // FIXME: Why do we JIT compile a method with `VERIFY_ERROR_FILLED_NEW_ARRAY` when - // `CanCompilerHandleVerificationFailure(VERIFY_ERROR_FILLED_NEW_ARRAY)` returns false? MaybeRecordStat(compilation_stats_, MethodCompilationStat::kNotCompiledMalformedOpcode); return false; } |