Hi Steven, > From: gcc-patches-ow...@gcc.gnu.org [mailto:gcc-patches- > ow...@gcc.gnu.org] On Behalf Of Steven Bosscher > Sent: 30 March 2013 13:10 > To: Jeff Law > Cc: GCC Patches > Subject: Re: [patch] Stop using JUMP_INSN for jump table data > > On Sat, Mar 30, 2013 at 2:02 PM, Jeff Law wrote: > > > OK. > > Thanks for the quick review! > > > Note that on at least one target, the jump table data is actual code > (PA). > > I don't think it makes a difference at this stage, but please keep > that in > > mind as you continue this work. > > Right, the PA "explodes" table jumps to individual jumps in > pa_reorg(). I actually tested on PA too (on my US$15 bargain HP > visualize J5600 workstation :-) and things work just fine. I'm more > concerned about some of the back ends that use > {next,prev}_{real,active}_insn to find jump table data after a > JUMP_INSN instead of using tablejump_p, but we'll see and I'll > obviously be on the hook to fix any fall-out.
Unfortunately, this patch breaks arm-none-eabi, arm-none-linux-gnueabi(hf) and aarch64-none-elf. See PR56809 for more info. GCC ICEs when building newlib and produces invalid assembly when building glibc. Any ideas? > > Ciao! > Steven Thanks, Kyrill
