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/94495] [10 Regression] Debug info size growth since r10-7515-g2c0fa3ecf70d199a
Date: Thu, 09 Apr 2020 09:33:27 +0000	[thread overview]
Message-ID: <bug-94495-4-vhSJh6oNzq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94495-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 48246
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48246&action=edit
gcc10-pr94495.patch

Untested fix.  This does two things during var-tracking.  One is try to reuse
even more the SP_DERIVED_VALUE_P and VALUEs equated to that + CONST_INT in
!frame_pointer_needed functions (ideally have just a single SP_DERIVED_VALUE_P)
and through that make sure they can be all expressed using cfa_base_rtx or
cfa_base_rtx + CONST_INT (and thus in DWARF using DW_OP_fbreg).
And the second change is that for VALUEs that can be expressed that way it
throws away all MO_VAL_SETs, we have the best expression for it (DW_OP_fbreg)
that is constant through the function, so it is not beneficial to express it in
one part of the function using that, in another part of the function using the
stack pointer, in yet another part using some other register.

  parent reply	other threads:[~2020-04-09  9:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-06  7:44 [Bug debug/94495] New: " marxin at gcc dot gnu.org
2020-04-06  7:44 ` [Bug debug/94495] " marxin at gcc dot gnu.org
2020-04-06  8:01 ` jakub at gcc dot gnu.org
2020-04-06 11:58 ` rguenth at gcc dot gnu.org
2020-04-06 13:14 ` marxin at gcc dot gnu.org
2020-04-06 13:34 ` marxin at gcc dot gnu.org
2020-04-06 17:07 ` jakub at gcc dot gnu.org
2020-04-08 15:25 ` jakub at gcc dot gnu.org
2020-04-09  9:33 ` jakub at gcc dot gnu.org [this message]
2020-04-09 19:21 ` cvs-commit at gcc dot gnu.org
2020-04-10  8:46 ` schwab@linux-m68k.org
2020-04-10 10:27 ` marxin at gcc dot gnu.org
2020-04-10 10:33 ` jakub at gcc dot gnu.org
2020-04-10 11:08 ` schwab@linux-m68k.org
2020-04-10 15:03 ` jakub at gcc dot gnu.org
2020-04-11  5:34 ` cvs-commit at gcc dot gnu.org
2020-04-14  9:29 ` jakub at gcc dot gnu.org
2020-04-15  5:41 ` marxin 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-94495-4-vhSJh6oNzq@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).