public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "yuri.karlsbrun at broadcom dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/101905] Missed debug information for global register variable
Date: Wed, 18 Aug 2021 20:42:15 +0000 [thread overview]
Message-ID: <bug-101905-4-I9p9EgMVND@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101905-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101905
--- Comment #3 from Yuri Karlsbrun <yuri.karlsbrun at broadcom dot com> ---
With the gcc-5.3 correct debug info for global register variable is written,
and variable is visible to gdb
gcc -v
Using built-in specs.
COLLECT_GCC=/tools/oss/packages/x86_64-centos7/gcc/5.3.0/bin/gcc
COLLECT_LTO_WRAPPER=/tools/oss/packages/x86_64-rhel7/gcc/5.3.0/bin/../libexec/gcc/x86_64-unknown-linux-gnu/5.3.0/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with: ../../gcc-5.3.0/configure
--prefix=/tools/oss/packages/x86_64-centos7/gcc/5.3.0 --with-gnu-as
--with-as=/tools/oss/packages/x86_64-centos7/binutils/2.25/bin/as --with-gnu-ld
--with-ld=/tools/oss/packages/x86_64-centos7/binutils/2.25/bin/ld
--with-mpc=/tools/oss/packages/x86_64-centos7/mpc/1.0.3
--with-mpfr=/tools/oss/packages/x86_64-centos7/mpfr/3.1.2
--enable-languages=c,c++,objc,java,fortran --enable-symvers=gnu
Thread model: posix
gcc version 5.3.0 (GCC)
< 1><0x00000075> DW_TAG_variable
DW_AT_name regVar
DW_AT_decl_file 0x00000001
/projects/play/ev.c
DW_AT_decl_line 0x00000001
DW_AT_type <0x00000082>
DW_AT_external yes(1)
DW_AT_location len 0x0001: 5f: DW_OP_reg15
next prev parent reply other threads:[~2021-08-18 20:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-14 2:19 [Bug debug/101905] New: " yuri.karlsbrun at broadcom dot com
2021-08-16 9:03 ` [Bug debug/101905] " rguenth at gcc dot gnu.org
2021-08-16 10:33 ` jakub at gcc dot gnu.org
2021-08-18 20:42 ` yuri.karlsbrun at broadcom dot com [this message]
2021-08-18 21:04 ` [Bug debug/101905] [9/10/11/12 Regression] " jakub at gcc dot gnu.org
2021-08-18 21:10 ` jakub at gcc dot gnu.org
2021-08-18 21:34 ` jakub at gcc dot gnu.org
2021-08-19 8:47 ` rguenth at gcc dot gnu.org
2021-08-20 11:33 ` jakub at gcc dot gnu.org
2021-08-20 12:49 ` rguenther at suse dot de
2021-08-23 9:51 ` cvs-commit at gcc dot gnu.org
2021-08-23 9:55 ` cvs-commit at gcc dot gnu.org
2021-08-23 10:05 ` [Bug debug/101905] [9/10 " jakub at gcc dot gnu.org
2022-05-10 8:20 ` cvs-commit at gcc dot gnu.org
2022-05-11 6:22 ` cvs-commit at gcc dot gnu.org
2022-05-11 6:36 ` 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-101905-4-I9p9EgMVND@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).