public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "roi.jacobson1 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/107513] [Feature Request] Implement __attribute__((__nodebug__))
Date: Thu, 03 Nov 2022 10:34:29 +0000	[thread overview]
Message-ID: <bug-107513-4-VBJpXI9Cdy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107513-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Roy Jacobson <roi.jacobson1 at gmail dot com> ---
I still think it might be good idea to introduce this for the sake of reducing
debug symbols size. I'm less interested in improving debug experience in this
case, but obviously any improvement to that is welcome as well.

  parent reply	other threads:[~2022-11-03 10:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-02 20:59 [Bug c++/107513] New: " roi.jacobson1 at gmail dot com
2022-11-02 21:06 ` [Bug c++/107513] " pinskia at gcc dot gnu.org
2022-11-02 21:23 ` roi.jacobson1 at gmail dot com
2022-11-02 21:32 ` pinskia at gcc dot gnu.org
2022-11-02 22:13 ` redi at gcc dot gnu.org
2022-11-03 10:34 ` roi.jacobson1 at gmail dot com [this message]
2023-10-31  3:14 ` redi at gcc dot gnu.org
2023-11-01 14:08 ` redi at gcc dot gnu.org

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-107513-4-VBJpXI9Cdy@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).