From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: gdb@sources.redhat.com
Subject: DW_OP_piece coming in gcc 3.4
Date: Fri, 30 Jan 2004 05:27:00 -0000 [thread overview]
Message-ID: <20040130052757.301704B104@berman.michael-chastain.com> (raw)
I'm getting this with gcc-3_4-branch -gdwarf-2:
(gdb) PASS: gdb.base/store.exp: up print old l - longest
print r^M
Unhandled dwarf expression opcode 0x93^M
(gdb) FAIL: gdb.base/store.exp: up print old r - longest
We need a strategic decision:
(1) Implement DW_OP_piece in time for gdb 6.1.
(2) Ask gcc to not emit DW_OP_piece in gcc 3.4.
(3) File a PR (or tag onto PR gdb/1312 but that's not really right),
KFAIL the tests, add a note to PROBLEMS.
I don't know which strategy is good for gdb.
What will it be?
Michael C
next reply other threads:[~2004-01-30 5:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-30 5:27 Michael Elizabeth Chastain [this message]
2004-01-30 5:52 ` Kevin Buettner
2004-01-30 15:06 ` Daniel Jacobowitz
2004-02-06 16:30 Fred Fish
2004-02-06 16:36 ` Daniel Jacobowitz
2004-02-16 19:25 ` Andrew Cagney
2004-02-16 19:42 ` Fred Fish
2004-02-17 7:39 ` Andreas Jaeger
2004-02-17 15:11 ` Daniel Jacobowitz
2004-02-18 6:42 ` Fred Fish
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=20040130052757.301704B104@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=gdb@sources.redhat.com \
/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