[Bug middle-end/106056] Missing call to targetm.asm_out.final_postscan_insn after processing an asm_input

piannetta at kalrayinc dot com gcc-bugzilla@gcc.gnu.org
Mon Jun 27 10:10:43 GMT 2022


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106056

--- Comment #2 from Paul Iannetta <piannetta at kalrayinc dot com> ---
Right now, I can't pinpoint a test-case within the official gcc testsuite, and
the list of targets which define TARGET_ASM_FINAL_POSTSCAN_INSN is limited to:
mips, avr and m68k.  From my understanding the only target that might be
affected is avr.

However, we maintain a VLIW target and rely on this hook to append our bundle
separator and there is a discrepancy between the treatment of extended asm and
basic asm blocks.

```
asm ("nop":::);
asm ("nop":::);
```

Each extended asm block triggers final_postscan and our bundle separator is
rightfully inserted.  However,

```
asm ("nop");
asm ("nop");
```

does not trigger final_postscan and the bundle separator is missing.


More information about the Gcc-bugs mailing list