public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "i at maskray dot me" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/99282] Emit .cfi_sections without arguments for -fno-asynchronous-unwind-tables
Date: Fri, 26 Feb 2021 23:17:40 +0000	[thread overview]
Message-ID: <bug-99282-4-7fIxWqXisX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99282-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Fangrui Song <i at maskray dot me> ---
(In reply to Jakub Jelinek from comment #1)
> There is the __GCC_HAVE_DWARF2_CFI_ASM predefined macro that tells if .cfi*
> directives are used or not.  And, inline asm that wishes to be usable in
> both can use that.

Thanks. I did not know this macro. So the user writing inline asm does have a
way to know whether .cfi_* should be inserted. If you think emitting
`.cfi_sections` is unnecessary, I am fine and happy that this is closed.

(GCC already generates `.cfi_sections .debug_frame\n`, so perhaps supporting
`.cfi_sections\n` is not that costly? :) Users will newer toolchain can be a
bit happier - they don't need to do `#ifdef __GCC_HAVE_DWARF2_CFI_ASM`).

      parent reply	other threads:[~2021-02-26 23:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-26  5:49 [Bug c/99282] New: " i at maskray dot me
2021-02-26 11:30 ` [Bug inline-asm/99282] " jakub at gcc dot gnu.org
2021-02-26 23:17 ` i at maskray dot me [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-99282-4-7fIxWqXisX@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).