search for: jtentrykind

...ction 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 it to the MachineJumpTableInfo::JTEntryKind enum? -- Richard Osborne | XMOS http://www.xmos.com -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: switch.s URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100302/dc46f567/attachment.ksh>

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

...renced. > Interesting. Any idea when that started happening? I'm pretty sure that didn't used to be the case. -Jim > 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 it to the MachineJumpTableInfo::JTEntryKind enum?