On 8/16/2021 11:06 AM, Jakub Jelinek via Gcc wrote:
On Mon, Aug 16, 2021 at 12:50:49PM -0400, Jason Merrill via Gcc wrote:
The trap builtin is target-specific. Making this system-specific (in
this case RTEMS) could be an issue.
Is that necessary?  Are there interesting targets that don't have a trap insn?
Depends on the definition of interesting.
I think avr, bpf, c6x, cr16, epiphany, fr30, frv, ft32, h8300, lm32, m32c, 
m32r, mcore,
mmix, mn10300, moxie, msp430, or1k, pdp11, pru, rl78, rx, sh, stormy16, v850 
and vax
don't have trap insn, while
aarch64, alpha, arc, arm, bfin, cris, csky, gcn, i386, ia64, iq2000, m68k, 
microblaze,
mips, nds32, nios2, nvptx, pa, riscv, rs6000, s390, sparc, tilegx, tilepro, 
visium and xtensa
have them.
Probably safer to say "no trap insn currently defined".  I'd bet multiple targets in the first set have trap insns defined in their ISA, but not in the MD file.

jeff

Reply via email to