From: Joel Brobecker <brobecker@gnat.com>
To: gdb-patches@sources.redhat.com
Subject: [RFA] New dwarf2_attribute_true_p function in dwarf2read.c (take 2)
Date: Fri, 16 Apr 2004 21:21:00 -0000 [thread overview]
Message-ID: <20040416212108.GJ22414@gnat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 617 bytes --]
Hello,
based on some comments made by Daniel in:
http://sources.redhat.com/ml/gdb-patches/2004-04/msg00352.html
here is a new version of the patch. This time, I only check the flag
for the DW_AT_declaration attribute. I also took this opportunity to
rework a bit the comments. It sounds like better English to me, this
time (any suggestion always welcome, btw).
2004-04-16 Joel Brobecker <brobecker@gnat.com>
* dwarf2read.c (dwarf2_attribute_true_p): New function.
(die_is_declaration): Use the function above. Add some comments.
Tested on x86-linux, no regression.
OK to apply?
--
Joel
[-- Attachment #2: true_p.diff --]
[-- Type: text/plain, Size: 2024 bytes --]
Index: dwarf2read.c
===================================================================
RCS file: /cvs/src/src/gdb/dwarf2read.c,v
retrieving revision 1.146
diff -u -p -r1.146 dwarf2read.c
--- dwarf2read.c 16 Apr 2004 16:12:52 -0000 1.146
+++ dwarf2read.c 16 Apr 2004 21:11:36 -0000
@@ -732,6 +732,9 @@ static void set_cu_language (unsigned in
static struct attribute *dwarf2_attr (struct die_info *, unsigned int,
struct dwarf2_cu *);
+static int dwarf2_attribute_true_p (struct die_info *die, unsigned name,
+ struct dwarf2_cu *cu);
+
static int die_is_declaration (struct die_info *, struct dwarf2_cu *cu);
static struct die_info *die_specification (struct die_info *die,
@@ -5549,11 +5552,30 @@ dwarf2_attr (struct die_info *die, unsig
return NULL;
}
+/* Return non-zero iff the attribute NAME is defined for the given DIE,
+ and holds a non-zero value. */
+
+static int
+dwarf2_attribute_true_p (struct die_info *die, unsigned name,
+ struct dwarf2_cu *cu)
+{
+ struct attribute *attr = dwarf2_attr (die, name, cu);
+
+ return (attr && DW_UNSND (attr));
+}
+
static int
die_is_declaration (struct die_info *die, struct dwarf2_cu *cu)
{
- return (dwarf2_attr (die, DW_AT_declaration, cu)
- && ! dwarf2_attr (die, DW_AT_specification, cu));
+ /* A DIE is a declaration if it has a DW_AT_declaration attribute
+ which value is non-zero. However, we have to be careful with
+ DIEs having a DW_AT_specification attribute, because dwarf2_attr()
+ (via dwarf2_attribute_true_p) follows this attribute. So we may
+ end up accidently finding a declaration attribute that belongs
+ to a different DIE referenced by the specification attribute,
+ even though the given DIE does not have a declaration attribute. */
+ return (dwarf2_attribute_true_p (die, DW_AT_declaration, cu)
+ && dwarf2_attr (die, DW_AT_specification, cu) == NULL);
}
/* Return the die giving the specification for DIE, if there is
next reply other threads:[~2004-04-16 21:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-16 21:21 Joel Brobecker [this message]
2004-04-19 12:42 ` Jim Blandy
2004-04-19 17:09 ` Joel Brobecker
2004-04-19 17:18 ` Daniel Jacobowitz
2004-04-19 17:25 ` Joel Brobecker
2004-04-19 18:03 ` Jim Blandy
2004-04-19 18:13 ` Joel Brobecker
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=20040416212108.GJ22414@gnat.com \
--to=brobecker@gnat.com \
--cc=gdb-patches@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