search for: ljti1_0

...ue, not a "assembly syntax" issue. ARM also has inline jump tables, how does it work? >> >> -Chris > I've attached the result of running llc -march=arm on test/CodeGen/XCore/switch.ll. The jump table entries are emitted twice, once inside the function after the label .LJTI1_0_0 and then again outside the function after the label .LJTI1_0. The .LJTI1_0 label at the start of the second set of jumptable entries is completely unreferenced. > Interesting. Any idea when that started happening? I'm pretty sure that didn't used to be the case. -Jim > Given tha...

...M also has inline jump tables, how does it work? >>>> >>>> -Chris >>>> >>> I've attached the result of running llc -march=arm on test/CodeGen/XCore/switch.ll. The jump table entries are emitted twice, once inside the function after the label .LJTI1_0_0 and then again outside the function after the label .LJTI1_0. The .LJTI1_0 label at the start of the second set of jumptable entries is completely unreferenced. >>> >> Interesting. Any idea when that started happening? I'm pretty sure that didn't used to be the case. &...

...ng" issue, not a "assembly syntax" issue. ARM also has inline jump tables, how does it work? > > -Chris I've attached the result of running llc -march=arm on test/CodeGen/XCore/switch.ll. The jump table entries are emitted twice, once inside the function after the label .LJTI1_0_0 and then again outside the function after the label .LJTI1_0. The .LJTI1_0 label at the start of the second set of jumptable entries is completely unreferenced. Given that MCAsmInfo is the wrong place would it make sense to describe it instead as a separate type of jump table encoding and add...

...quot; issue. ARM also has inline jump tables, how does it work? >>> >>> -Chris >>> >> I've attached the result of running llc -march=arm on test/CodeGen/XCore/switch.ll. The jump table entries are emitted twice, once inside the function after the label .LJTI1_0_0 and then again outside the function after the label .LJTI1_0. The .LJTI1_0 label at the start of the second set of jumptable entries is completely unreferenced. >> > Interesting. Any idea when that started happening? I'm pretty sure that didn't used to be the case. > &gt...

On Mar 1, 2010, at 10:52 AM, Richard Osborne wrote: > On 23/02/10 14:58, Richard Osborne wrote: >> I've recently changed the XCore target to implement BR_JT as a jump to a >> series jumps. The jump table entries are expand inline in the function >> so there is no longer a need to emit jump tables at the end of the >> function. However the emission of jump tables at

...t work? >>>>> >>>>> -Chris >>>>> >>>>> >>>> I've attached the result of running llc -march=arm on test/CodeGen/XCore/switch.ll. The jump table entries are emitted twice, once inside the function after the label .LJTI1_0_0 and then again outside the function after the label .LJTI1_0. The .LJTI1_0 label at the start of the second set of jumptable entries is completely unreferenced. >>>> >>>> >>> Interesting. Any idea when that started happening? I'm pretty sure that did...