From: Jim Blandy <jimb@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb@sources.redhat.com
Subject: dwarf2read.c doesn't produce LOC_COMPUTED_ARG
Date: Thu, 10 Apr 2003 04:26:00 -0000 [thread overview]
Message-ID: <vt2znmzou34.fsf@zenia.red-bean.com> (raw)
I just realized that dwarf2read.c will produce LOC_COMPUTED symbols,
but not LOC_COMPUTED_ARG symbols. The case for
DW_TAG_formal_parameter in new_symbol doesn't call
var_decode_location; it does what it's always done.
Is there any reason for this, or was it just an oversight?
next reply other threads:[~2003-04-10 4:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-10 4:26 Jim Blandy [this message]
2003-04-10 12:33 ` Daniel Jacobowitz
2003-04-10 22:15 ` Jim Blandy
2003-04-10 22:32 ` Daniel Berlin
2003-04-11 2:18 ` Andrew Cagney
2003-04-10 13:30 ` Daniel Berlin
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=vt2znmzou34.fsf@zenia.red-bean.com \
--to=jimb@redhat.com \
--cc=drow@mvista.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