This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [patch] Stop using JUMP_INSN for jump table data

From: Jeff Law <law at redhat dot com>
To: Steven Bosscher <stevenb dot gcc at gmail dot com>
Cc: GCC Patches <gcc-patches at gcc dot gnu dot org>
Date: Sat, 30 Mar 2013 07:21:12 -0600
Subject: Re: [patch] Stop using JUMP_INSN for jump table data
References: <CABu31nOPJ-+ixTfOqAGWMqg4nbKXHP_OWuitre8=1H__cc8S+Q at mail dot gmail dot com> <5156E26B dot 7040503 at redhat dot com> <CABu31nNZnfmkR2Tm8GxZVg+vL3t-BbTo3yGM0jHBepDCkN7BWQ at mail dot gmail dot com>

On 03/30/2013 07:10 AM, Steven Bosscher wrote:


Right, the PA "explodes" table jumps to individual jumps in
pa_reorg().

Yup. One of the many things I'd like to forget. Unlike other jumps onthe PA, we can't nullify the delay slot to save space. The jump mustalways be 2 instructions. So we have to have a separate pattern, eventhough it looks like the normal jump. Ugh.

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.

I won't be surprised if we find this stuff, but I don't think there'llbe anything inherently difficult about fixing it.


jeff

References:
- [patch] Stop using JUMP_INSN for jump table data
  - From: Steven Bosscher
- Re: [patch] Stop using JUMP_INSN for jump table data
  - From: Jeff Law
- Re: [patch] Stop using JUMP_INSN for jump table data
  - From: Steven Bosscher

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]