public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "piannetta at kalrayinc dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/106056] Missing call to targetm.asm_out.final_postscan_insn after processing an asm_input
Date: Mon, 27 Jun 2022 10:10:43 +0000	[thread overview]
Message-ID: <bug-106056-4-R6L7WYdcip@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106056-4@http.gcc.gnu.org/bugzilla/>

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.

      parent reply	other threads:[~2022-06-27 10:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-22 12:50 [Bug target/106056] New: " piannetta at kalrayinc dot com
2022-06-27  8:49 ` [Bug middle-end/106056] " marxin at gcc dot gnu.org
2022-06-27 10:10 ` piannetta at kalrayinc dot com [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-106056-4-R6L7WYdcip@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).