| Issue |
173813
|
| Summary |
[BOLT]Multiple warnings about indirect branches and indirect tails appear when using BOLT optimization.
|
| Labels |
BOLT
|
| Assignees |
|
| Reporter |
jiovf
|
When optimizing `libart.so` with BOLT, thousands of warnings appear, primarily of the following types:
1.
```
BOLT-WARNING: sizes differ for function ExecuteNterpImpl/1. FDE : 58928; symbol table : 1888. Using max size.
BOLT-INFO: skipping possibly another entry for function ExecuteNterpImpl/1(*4) : artNterpAsmInstructionStart/1
BOLT-INFO: using nterp_op_nop/1 as another entry to function ExecuteNterpImpl/1(*4)
```
2.
```
BOLT-INFO: rejected potential indirect tail call in function _ZN3art17GetResolvedMethodEPNS_9ArtMethodERKNS_8CodeInfoERKNS_13BitTableRangeINS_10InlineInfoEEE/1(*2) in basic block .Ltmp4930.
BOLT-WARNING: failed to post-process indirect branches for _ZN3art17GetResolvedMethodEPNS_9ArtMethodERKNS_8CodeInfoERKNS_13BitTableRangeINS_10InlineInfoEEE/1(*2)
BOLT-INFO: rejected potential indirect tail call in function _ZN3art16IntrinsicVisitor8DispatchEPNS_7HInvokeE/1(*2) in basic block .Ltmp8856.
```
3.
```
BOLT-WARNING: cannot update ranges for DIE in Unit offset 0x198a99
BOLT-WARNING: cannot update ranges for DIE in Unit offset 0x199a7c
```
4.
```
BOLT-INFO: not writing section header for section .data.rel.ro
BOLT-INFO: not writing section header for section .fini_array
BOLT-INFO: not writing section header for section .init_array
BOLT-INFO: not writing section header for section .data
```
Do these warnings indicate that BOLT is unable to properly handle `libart.so`? I attempted to replace the original file with the optimized libart.bolt, and the system did indeed crash.
![]()
_______________________________________________
llvm-bugs mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
