public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Pierre-Marie de Rodat <derodat@adacore.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 2/2] DWARF: make it possible to emit debug info for declarations only
Date: Tue, 20 Jun 2017 14:34:00 -0000	[thread overview]
Message-ID: <49e45f2c-80b1-16ee-a2f7-05bfd067cd2d@adacore.com> (raw)
In-Reply-To: <CAFiYyc1LS0pps+RURi0OpkgoT9Ha-ToP9JXf6acN3mj3UsRkKw@mail.gmail.com>

On 06/20/2017 02:16 PM, Richard Biener wrote:
> Nice.  This looks ok.

Great, thank you!

> I'm mildy curious about the deecrease of debuginfo size for cc1 -- did
> you spot anything obvious there?

Well, the benchmark I exposed was for the whole file size, not just 
.debug_info section size. Just to be sure, I compared object files for 
both trunk and my patched tree: outside of Ada units, I only get the 
following evolution:
> gcc/dwarf2out.o: -10168 bytes
> gcc/godump.o: +272 bytes
> gcc/passes.o: +880 bytes

This diff comes from my changes themselves. I had a quick look at the 
same for cc1’s .debug_info: there is the expected evolution, too,

> I suspect Fortran wants to do sth similar as Ada for imported modules.

Maybe. I have zero Fortran knowledge, so I’ll let a Fortran expert 
decide, if that is fine for you. :-) In any case, the back-end is ready 
for that.

-- 
Pierre-Marie de Rodat

  reply	other threads:[~2017-06-20 14:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-29  7:50 [PATCH 1/2] gimplify_modify_expr: avoid DECL_DEBUG_EXPR links across functions Pierre-Marie de Rodat
2017-05-29  8:05 ` [PATCH 2/2] DWARF: make it possible to emit debug info for declarations only Pierre-Marie de Rodat
2017-05-29 13:39   ` Pierre-Marie de Rodat
2017-05-30 12:11   ` Richard Biener
2017-05-30 15:51     ` Pierre-Marie de Rodat
2017-05-31  7:37       ` Richard Biener
2017-05-31  9:12         ` Pierre-Marie de Rodat
2017-06-16 16:35           ` Pierre-Marie de Rodat
2017-06-20 12:16             ` Richard Biener
2017-06-20 14:34               ` Pierre-Marie de Rodat [this message]
2017-06-21  7:11                 ` Richard Biener
2017-06-21 11:25                   ` Pierre-Marie de Rodat
2017-05-30 11:59 ` [PATCH 1/2] gimplify_modify_expr: avoid DECL_DEBUG_EXPR links across functions Richard Biener
2017-05-30 15:35   ` Pierre-Marie de Rodat

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=49e45f2c-80b1-16ee-a2f7-05bfd067cd2d@adacore.com \
    --to=derodat@adacore.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=richard.guenther@gmail.com \
    /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).