search for: ljti8485_1_1

...he jumptable in the constant pool immediately after it. Displacement from the pc in this case is #1476 which is way above magic #1020 hence the error after fixup. Both ARMCodeEmitter::emitLEApcrelJTInstruction() and emitJumpTableAddress() are responsible for the offending instruction adr r0, #.LJTI8485_1_1 But besides the fact that they do not complain about the invalid offset from the pc I do not see anything wrong here. The problem seems to be in the ARMConstantIslands which is not splitting BB#671 into smaller pieces and thus producing over the limit 'add' opcode. This code fragment be...

...t. >> Displacement from the pc >> in this case is #1476 which is way above magic #1020 hence the error >> after fixup. >> Both ARMCodeEmitter::emitLEApcrelJTInstruction() and >> emitJumpTableAddress() >> are responsible for the offending instruction adr r0, #.LJTI8485_1_1 >> But besides the fact that they do not complain about the invalid offset >> from the pc I do not see >> anything wrong here. >> >> The problem seems to be in the ARMConstantIslands which is not splitting >> BB#671 into >> smaller pieces and thus producing...

...ediately after it. > Displacement from the pc > in this case is #1476 which is way above magic #1020 hence the error > after fixup. > Both ARMCodeEmitter::emitLEApcrelJTInstruction() and > emitJumpTableAddress() > are responsible for the offending instruction adr r0, > #.LJTI8485_1_1 > But besides the fact that they do not complain about the invalid > offset > from the pc I do not see > anything wrong here. > > The problem seems to be in the ARMConstantIslands which is not > splitting > BB#671 into > smaller pieces and thus producing over the limi...

...>>> in this case is #1476 which is way above magic #1020 hence the error >>> after fixup. >>> Both ARMCodeEmitter::emitLEApcrelJTInstruction() and >>> emitJumpTableAddress() >>> are responsible for the offending instruction adr r0, >>> #.LJTI8485_1_1 >>> But besides the fact that they do not complain about the invalid >>> offset >>> from the pc I do not see >>> anything wrong here. >>> >>> The problem seems to be in the ARMConstantIslands which is not >>> splitting >>>...