public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl at lucon dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/19124] [4.0 regression] gcc generates incorrect dwarf2 debug info
Date: Thu, 30 Dec 2004 21:01:00 -0000 [thread overview]
Message-ID: <20041230210122.18312.qmail@sourceware.org> (raw)
In-Reply-To: <20041222003609.19124.hjl@lucon.org>
------- Additional Comments From hjl at lucon dot org 2004-12-30 21:01 -------
insn-preds.o was compiled with
stage2/xgcc -Bstage2/ -B/usr/gcc-4.0/i686-pc-linux-gnu/bin/ -c -O2 -g -fomit-
frame-pointer -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -
Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wold-style-
definition -Werror -DHAVE_CONFIG_H -I. -I. -
I/net/gnu/export/gnu/src/gcc/gcc/gcc -I/net/gnu/export/gnu/src/gcc/gcc/gcc/. -
I/net/gnu/export/gnu/src/gcc/gcc/gcc/../include -
I/net/gnu/export/gnu/src/gcc/gcc/gcc/../libcpp/include insn-preds.c -o insn-
preds.o
It generates
<1><418c>: Abbrev Number: 47 (DW_TAG_subprogram)
DW_AT_sibling : <41c6>
DW_AT_external : 1
DW_AT_name : (indirect string, offset: 0x3133):
tls_symbolic_operand
DW_AT_decl_file : 1
DW_AT_decl_line : 471
DW_AT_prototyped : 1
DW_AT_type : <2c>
DW_AT_low_pc : 0x2f0
DW_AT_high_pc : 0x31c
<2><41a6>: Abbrev Number: 48 (DW_TAG_formal_parameter)
DW_AT_name : op
DW_AT_decl_file : 1
DW_AT_decl_line : 470
DW_AT_type : <2dc>
DW_AT_location : 549 (location list)
<2><41b5>: Abbrev Number: 49 (DW_TAG_formal_parameter)
DW_AT_name : (indirect string, offset: 0x44e5): mode
DW_AT_decl_file : 1
DW_AT_decl_line : 470
DW_AT_type : <6be>
DW_AT_location : 5a2 (location list)
00000549 000002f0 000002fe (DW_OP_fbreg: 4)
00000549 000002fe 00000300 (DW_OP_reg0)
00000549 00000300 00000301 (DW_OP_fbreg: 4)
00000549 00000301 0000030b (DW_OP_reg0)
00000549 0000030b 00000311 (DW_OP_fbreg: 4)
00000549 00000311 00000315 (DW_OP_reg0)
00000549 00000315 0000031c (DW_OP_fbreg: 4)
000005a2 000002f0 000002fe (DW_OP_fbreg: 8)
000005a2 000002fe 0000031c (DW_OP_reg2)
There is no DW_AT_frame_base. According to DWARF 3 spec, DW_OP_fbreg needs
DW_AT_frame_base.
--
What |Removed |Added
----------------------------------------------------------------------------
Keywords|patch |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19124
next prev parent reply other threads:[~2004-12-30 21:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-22 0:36 [Bug debug/19124] New: " hjl at lucon dot org
2004-12-22 0:53 ` [Bug debug/19124] " hjl at lucon dot org
2004-12-22 1:09 ` hjl at lucon dot org
2004-12-22 1:12 ` pinskia at gcc dot gnu dot org
2004-12-22 1:34 ` pinskia at gcc dot gnu dot org
2004-12-22 13:07 ` steven at gcc dot gnu dot org
2004-12-26 0:56 ` dberlin at gcc dot gnu dot org
2004-12-28 2:34 ` pinskia at gcc dot gnu dot org
2004-12-28 18:39 ` hjl at lucon dot org
2004-12-28 18:49 ` dberlin at dberlin dot org
2004-12-30 3:38 ` hjl at lucon dot org
2004-12-30 5:10 ` dberlin at dberlin dot org
2004-12-30 21:01 ` hjl at lucon dot org [this message]
2005-01-02 20:29 ` dberlin at gcc dot gnu dot org
2005-01-04 20:07 ` ac131313 at redhat dot com
2005-01-10 16:45 ` dberlin at dberlin dot org
2005-01-10 18:32 ` dberlin at gcc dot gnu dot org
2005-01-10 18:55 ` hjl at lucon dot org
2005-01-10 22:37 ` hjl at lucon dot org
2005-01-20 20:10 ` cvs-commit at gcc dot gnu dot org
2005-01-20 20:15 ` dberlin 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=20041230210122.18312.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: 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).