public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mark at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/51902] lexical_blocks inside inlined_subroutines generate duplicate debug_ranges Date: Sat, 21 Jan 2012 05:23:00 -0000 [thread overview] Message-ID: <bug-51902-4-JXgbDhmTsH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51902-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51902 Mark Wielaard <mark at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #26380|0 |1 is obsolete| | --- Comment #6 from Mark Wielaard <mark at gcc dot gnu.org> 2012-01-21 00:33:03 UTC --- Created attachment 26399 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26399 debug_ranges.c - Get some statistics on .debug_ranges section. Here is a slightly tweaked version of debug_ranges.c that also recognizes nested lexical_blocks and will print which dies/ranges it finds that are equal, but are at different range offsets. die [ed] and [d3] use range [40] and [0], 6 equal addresses. die [100] and [ed] use range [80] and [40], 6 equal addresses. die [10c] and [100] use range [c0] and [80], 6 equal addresses. die [11f] and [10c] use range [100] and [c0], 6 equal addresses. cus: 1 subprograms: 2 inlined_subroutines: 1 lexical_blocks: 4 equal_ranges: 0 shared_addrs: 0 dup_ranges: 4 dup_addrs: 24
next prev parent reply other threads:[~2012-01-21 0:33 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-19 15:01 [Bug debug/51902] New: " mark at gcc dot gnu.org 2012-01-19 18:55 ` [Bug debug/51902] " jakub at gcc dot gnu.org 2012-01-20 11:30 ` jakub at gcc dot gnu.org 2012-01-20 14:19 ` mark at gcc dot gnu.org 2012-01-20 14:20 ` jakub at gcc dot gnu.org 2012-01-20 18:01 ` jakub at gcc dot gnu.org 2012-01-21 5:23 ` mark at gcc dot gnu.org [this message] 2012-01-23 15:33 ` jakub at gcc dot gnu.org 2012-01-24 10:37 ` jakub at gcc dot gnu.org 2012-03-05 20:18 ` jakub at gcc dot gnu.org 2012-03-06 17:43 ` jakub 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-51902-4-JXgbDhmTsH@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: linkBe 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).