jump_table_data and active_insn_p

[Paulo Matos]

Why is jump_table_data an active_insn?
int
active_insn_p (const_rtx insn)
{
  return (CALL_P (insn) || JUMP_P (insn)
          || JUMP_TABLE_DATA_P (insn) /* FIXME */
          || (NONJUMP_INSN_P (insn)
              && (! reload_completed
                  || (GET_CODE (PATTERN (insn)) != USE
                      && GET_CODE (PATTERN (insn)) != CLOBBER))));
}

It is clear that someone [Steven Bosscher] thought it needs fixing but what's 
the problem with just removing it from the OR-expression?

Cheers,

Paulo Matos