public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/48853] [4.7 Regression] Wrong DWARF codegen when Pmode != ptr_mode
Date: Wed, 04 May 2011 17:33:00 -0000 [thread overview]
Message-ID: <bug-48853-4-Nggpjl0P2U@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48853-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48853
--- Comment #12 from H.J. Lu <hjl.tools at gmail dot com> 2011-05-04 17:24:24 UTC ---
(In reply to comment #11)
> Created attachment 24183 [details]
> gcc47-pr48853.patch
>
> Is this better?
No, it doesn't handle DW_OP_GNU_const_type:
(gdb) f 0
#0 mem_loc_descriptor (rtl=0x7ffff0de42f0, mode=DImode, mem_mode=DImode,
initialized=VAR_INIT_STATUS_INITIALIZED)
at /export/gnu/import/git/gcc-x32/gcc/dwarf2out.c:14350
14350 mem_loc_result = new_loc_descr (DW_OP_GNU_const_type, 0,
(gdb) bt
#0 mem_loc_descriptor (rtl=0x7ffff0de42f0, mode=DImode, mem_mode=DImode,
initialized=VAR_INIT_STATUS_INITIALIZED)
at /export/gnu/import/git/gcc-x32/gcc/dwarf2out.c:14350
#1 0x0000000000b3b39d in mem_loc_descriptor (rtl=0x7ffff0d47f90, mode=DImode,
mem_mode=DImode, initialized=VAR_INIT_STATUS_INITIALIZED)
at /export/gnu/import/git/gcc-x32/gcc/dwarf2out.c:14212
#2 0x0000000000b1bed6 in dwarf2out_frame_debug_cfa_expression (
set=0x7ffff0d47fc0, label=0x4a8ee40 "<do not output>")
at /export/gnu/import/git/gcc-x32/gcc/dwarf2out.c:2088
#3 0x0000000000b1d605 in dwarf2out_frame_debug (insn=0x7ffff0d45a20,
after_p=1 '\001') at /export/gnu/import/git/gcc-x32/gcc/dwarf2out.c:2870
#4 0x0000000000c9a66c in final_scan_insn (insn=0x7ffff0d45a20,
file=0x4c05540, optimize_p=2, nopeepholes=0, seen=0x7fffffffddac)
at /export/gnu/import/git/gcc-x32/gcc/final.c:2775
#5 0x0000000000c98ae7 in final (first=0x7ffff0ce95c0, file=0x4c05540,
optimize_p=2) at /export/gnu/import/git/gcc-x32/gcc/final.c:1795
#6 0x0000000000c9cfb4 in rest_of_handle_final ()
at /export/gnu/import/git/gcc-x32/gcc/final.c:4246
#7 0x000000000133ac82 in execute_one_pass (pass=0x4a80a00)
at /export/gnu/import/git/gcc-x32/gcc/passes.c:1556
#8 0x000000000133ae71 in execute_pass_list (pass=0x4a80a00)
at /export/gnu/import/git/gcc-x32/gcc/passes.c:1611
#9 0x000000000133ae92 in execute_pass_list (pass=0x4a813e0)
---Type <return> to continue, or q <return> to quit---q
at /export/gnu/impoQuit
(gdb) f 1
#1 0x0000000000b3b39d in mem_loc_descriptor (rtl=0x7ffff0d47f90, mode=DImode,
mem_mode=DImode, initialized=VAR_INIT_STATUS_INITIALIZED)
at /export/gnu/import/git/gcc-x32/gcc/dwarf2out.c:14212
14212 dw_loc_descr_ref mem_loc_result2
(gdb) call debug_rtx (rtl)
(plus:DI (reg/f:DI 6 bp)
(const_int -24 [0xffffffffffffffe8]))
(gdb)
We need to check all those new DW_OP_GNU_xxxx ops.
next prev parent reply other threads:[~2011-05-04 17:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-03 13:40 [Bug debug/48853] New: " hjl.tools at gmail dot com
2011-05-03 13:55 ` [Bug debug/48853] " jakub at gcc dot gnu.org
2011-05-03 14:07 ` hjl.tools at gmail dot com
2011-05-03 15:10 ` sje at cup dot hp.com
2011-05-03 15:28 ` hjl.tools at gmail dot com
2011-05-03 16:08 ` jakub at gcc dot gnu.org
2011-05-03 22:18 ` sje at cup dot hp.com
2011-05-04 7:44 ` jakub at gcc dot gnu.org
2011-05-04 13:44 ` hjl.tools at gmail dot com
2011-05-04 14:08 ` jakub at gcc dot gnu.org
2011-05-04 15:43 ` hjl.tools at gmail dot com
2011-05-04 17:20 ` jakub at gcc dot gnu.org
2011-05-04 17:33 ` hjl.tools at gmail dot com [this message]
2011-05-04 18:15 ` jakub at gcc dot gnu.org
2011-05-04 18:16 ` hjl.tools at gmail dot com
2011-05-04 20:04 ` hjl.tools at gmail dot com
2011-05-05 15:50 ` jakub at gcc dot gnu.org
2011-05-06 22:39 ` hjl.tools at gmail dot com
2011-05-06 22:51 ` hjl.tools at gmail dot com
2011-05-06 22:55 ` hjl.tools at gmail dot com
2011-05-06 23:04 ` sje at cup dot hp.com
2011-05-09 18:21 ` hjl at gcc dot gnu.org
2011-08-01 14:27 ` rguenth at gcc dot gnu.org
2011-08-02 14:06 ` rguenth at gcc dot gnu.org
2011-08-02 14:28 ` hjl.tools at gmail dot com
2011-10-10 11:52 ` rguenth 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-48853-4-Nggpjl0P2U@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).