public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/102523] Assume -fvar-tracking -fvar-tracking-assignments when compiling with -O0 -g
Date: Tue, 28 Sep 2021 20:41:04 +0000	[thread overview]
Message-ID: <bug-102523-4-2xALJFeHoL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102523-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
This can't be done.  -O0's main objective is fast compile time, -fvar-tracking*
is very expensive compile time.
What we want is instead a special var-tracking mode that would track only what
is necessary for -O0 where most of the variables live in memory.
In particular, one needs to track variables with register keyword (those aren't
pinned into memory), probably passing of parameters and return values in the
prologue and epilogue and probably VLA dimensions in some cases.
Note, -Og, while it does var-tracking and generally attempts to disable many
optimizations that could hurt debuggability unfortunately doesn't add
artificial uses of all vars at the end of their scope and so sometimes -O0 -g
is debuggable much better than -Og -g, sometimes the other way around.

      parent reply	other threads:[~2021-09-28 20:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-28 20:04 [Bug debug/102523] New: " woodard at redhat dot com
2021-09-28 20:11 ` [Bug debug/102523] " pinskia at gcc dot gnu.org
2021-09-28 20:41 ` jakub at gcc dot gnu.org [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-102523-4-2xALJFeHoL@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).