public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/23551] dwarf records for inlines appear incomplete Date: Sat, 09 Dec 2006 05:43:00 -0000 [thread overview] Message-ID: <20061209054335.12740.qmail@sourceware.org> (raw) In-Reply-To: <bug-23551-8732@http.gcc.gnu.org/bugzilla/> ------- Comment #12 from pinskia at gcc dot gnu dot org 2006-12-09 05:43 ------- Case 2 was filed as PR 29792 and was declared invalid. Though we get currently: .uleb128 0x2 # (DIE (0x25) DW_TAG_subprogram) .ascii "foo\0" # DW_AT_name .byte 0x1 # DW_AT_decl_file (no-inlined-instance-record.c) .byte 0x2 # DW_AT_decl_line .byte 0x1 # DW_AT_prototyped .long 0x40 # DW_AT_type .byte 0x3 # DW_AT_inline .long 0x40 # DW_AT_sibling .uleb128 0x3 # (DIE (0x36) DW_TAG_formal_parameter) .ascii "x\0" # DW_AT_name .byte 0x1 # DW_AT_decl_file (no-inlined-instance-record.c) .byte 0x1 # DW_AT_decl_line .long 0x40 # DW_AT_type .byte 0x0 # end of children of DIE 0x25 Case 1, is also too hard to fix as it would make us lose a lot of optimizations. Really what GCC is producing is the best debugging you can get for these functions. -- pinskia at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23551
next prev parent reply other threads:[~2006-12-09 5:43 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-23551-8732@http.gcc.gnu.org/bugzilla/> 2005-10-13 2:47 ` wilson at gcc dot gnu dot org 2006-07-21 16:57 ` drow at gcc dot gnu dot org 2006-11-01 6:37 ` aoliva at gcc dot gnu dot org 2006-12-09 5:43 ` pinskia at gcc dot gnu dot org [this message] 2007-03-30 18:21 ` fche at redhat dot com 2007-03-30 21:04 ` pinskia at gcc dot gnu dot org 2007-03-30 21:10 ` fche at redhat dot com 2007-05-10 7:40 ` patchapp at dberlin dot org 2007-07-06 8:39 ` aoliva at gcc dot gnu dot org 2007-07-09 19:24 ` aoliva at gcc dot gnu dot org [not found] <bug-23551-4@http.gcc.gnu.org/bugzilla/> 2011-04-21 14:08 ` mfortune at gmail dot com 2024-01-26 13:43 ` rguenth at gcc dot gnu.org 2005-08-24 20:52 [Bug debug/23551] New: " graydon at redhat dot com 2005-08-24 20:52 ` [Bug debug/23551] " graydon at redhat dot com 2005-08-24 20:53 ` graydon at redhat dot com 2005-08-24 20:54 ` graydon at redhat dot com 2005-08-24 20:55 ` graydon at redhat dot com 2005-08-24 20:55 ` graydon at redhat dot com 2005-08-24 20:59 ` graydon at redhat dot com 2005-08-24 21:09 ` graydon at redhat dot com 2005-08-24 21:58 ` pinskia at gcc dot gnu dot 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=20061209054335.12740.qmail@sourceware.org \ --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).