Issue

https://gitcode.com/openharmony/arkcompiler_ets_frontend/issues/8972

Reason

Add missing cte for late-init obj literal

Description

Add missing cte for late-init obj literal

Tests

ninja all tests

All required pre-merge tests passed. Results are available in the internal CI.

Functional Testing (Mandatory unless the change only involves text) wiki

1. es2abc Test Cases (Debug Mode)

• Passed
• Not applicable, no need to verify

2. Verifier Testing

• Passed
• Not applicable, no need to verify

3. 64-bit RK Compilation

• Passed
• Not applicable, no need to verify

4. Compile macOS SDK

• Passed
• Not applicable, no need to verify

Obfuscation Testing (Mandatory if ArkGuard-related changes are involved) wiki

1. Unit Tests

• Passed
• Not applicable, no need to verify

2. Compiler Test Suite

• Passed
• Not applicable, no need to verify

3. TSC Extra Test Suite

• Passed
• Not applicable, no need to verify

4. Test262 Test Suite

• Passed
• Not applicable, no need to verify

5. Benchmark Tests

• Passed
• Not applicable, no need to verify

6. Automated Application Test Suite

• Passed
• Not applicable, no need to verify

7. Global Variable Check — Were any global variables created? If so, were they cleared?

• Global variables created and cleared
• Global variables created but not cleared
• No global variables created

Compatibility Testing (for instruction generation or file format changes)

1. Minor Version Compatibility Test

• Version number added
• Passed
• Not applicable, no need to verify

2. Major Version Compatibility Test

• Passed
• Not applicable, no need to verify

3. es2abc Version Compatibility Test
   Note: If the PR involves changes to version control test cases, you must also check its impact on other branches and confirm whether updates are needed in those branches.

• Affected — Changes impact API/bytecode version and need to be synced to other branches
• Affected — Changes impact API/bytecode version but do not need to be synced to other branches
• Not affected — Changes do not involve API/bytecode version

4. Compatibility Testing for Lexical Environment Changes
   Note: If the PR involves modifications to the lexical environment, verify whether it is compatible with hot reload scenarios.

• Involved, affects hot reload scenarios, requires impact assessment
• Involved, does not affect hot reload scenarios
• Not involved

Performance Testing (e.g., new syntax checking scenarios)

• Passed
• Not applicable, no need to verify

Command/abc format modification self-check, please contact the email below, synchronize to the relevant field

Important: For modifications involving the abc2program, libpandafile and isa directories in the runtime_core repository, you must provide a compiled hap package for the helloworld project to the corresponding domain and contact the email address below.

• Involved, already synchronized
• Not involved

Email: wutao185@huawei.com