public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tausq at debian dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/15860] New: [3.3/3.4/3.5 regression] No DW_AT_location debug info is emitted for formal arguments to a function that uses "register" qualifiers Date: Mon, 07 Jun 2004 18:25:00 -0000 [thread overview] Message-ID: <20040607182512.15860.tausq@debian.org> (raw) Compile the attached code with "gcc -g -c structs2.c" [structs2.c comes from the gdb testsuite] The arguments to param_reg() are not described in the dwarf debug info. e.g.: $ readelf -wi structs2.o [...] <2><69>: Abbrev Number: 6 (DW_TAG_formal_parameter) DW_AT_name : (indirect string, offset: 0x27): pr_char DW_AT_decl_file : 1 DW_AT_decl_line : 28 DW_AT_type : <96> No DW_AT_location information is given. With gcc-3.0, I see: <2><82>: Abbrev Number: 6 (DW_TAG_formal_parameter) DW_AT_name : pr_char DW_AT_decl_file : 1 DW_AT_decl_line : 28 DW_AT_type : <cf> DW_AT_location : 2 byte block: 91 b (DW_OP_fbreg: 11) param_reg() is defined as: static void param_reg (register signed char pr_char, register unsigned char pr_uchar, register short pr_short, register unsigned short pr_ushort); if the "register" qualifier is removed, the correct debug information is emitted. Dan Jacobowitz tells me that on i386/mips, with gcc-3.3, he does not see this problem. On hppa-linux i see this with gcc-3.3/3.4/3.5 This was also observed by Corinna Vinschen (sh target): http://sources.redhat.com/ml/gdb/2004-03/msg00043.html -- Summary: [3.3/3.4/3.5 regression] No DW_AT_location debug info is emitted for formal arguments to a function that uses "register" qualifiers Product: gcc Version: 3.5.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: debug AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: tausq at debian dot org CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: hppa-unknown-linux GCC host triplet: hppa-unknown-linux GCC target triplet: hppa-unknown-linux http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15860
next reply other threads:[~2004-06-07 18:25 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-06-07 18:25 tausq at debian dot org [this message] 2004-06-07 18:26 ` [Bug debug/15860] " tausq at debian dot org 2004-06-07 18:52 ` pinskia at gcc dot gnu dot org 2004-08-07 22:37 ` pinskia at gcc dot gnu dot org 2004-08-12 7:59 ` steven at gcc dot gnu dot org 2004-08-29 18:53 ` mmitchel at gcc dot gnu dot org 2004-10-13 18:54 ` [Bug debug/15860] [3.3/3.4/4.0 " rth at gcc dot gnu dot org 2004-10-13 18:57 ` rth at gcc dot gnu dot org 2004-10-13 21:24 ` tausq at debian dot org 2004-10-13 23:44 ` cvs-commit at gcc dot gnu dot org 2004-10-13 23:44 ` cvs-commit at gcc dot gnu dot org 2004-10-13 23:45 ` rth at gcc dot gnu dot org 2004-10-14 1:45 ` giovannibajo at libero dot it
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=20040607182512.15860.tausq@debian.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).