From: Joel Brobecker <brobecker@gnat.com>
To: gdb-patches@sources.redhat.com
Subject: [RFA] New dwarf2_attribute_true_p function in dwarf2read.c
Date: Thu, 15 Apr 2004 20:23:00 -0000 [thread overview]
Message-ID: <20040415202318.GD1564@gnat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 380 bytes --]
Hello,
Following a suggestion made by JimB in:
http://sources.redhat.com/ml/gdb-patches/2004-04/msg00297.html
I made the following change:
2004-04-15 Joel Brobecker <brobecker@gnat.com>
* dwarf2read.c (dwarf2_attribute_true_p): New function.
(die_is_declaration): Use the function above.
Tested on x86-linux, no regression.
OK to apply?
Thanks,
--
Joel
[-- Attachment #2: dwarf2read.c.diff --]
[-- Type: text/plain, Size: 1894 bytes --]
Index: dwarf2read.c
===================================================================
RCS file: /cvs/src/src/gdb/dwarf2read.c,v
retrieving revision 1.142
diff -u -p -r1.142 dwarf2read.c
--- dwarf2read.c 2 Apr 2004 04:35:46 -0000 1.142
+++ dwarf2read.c 15 Apr 2004 20:20:15 -0000
@@ -677,6 +677,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,
@@ -5141,11 +5144,28 @@ 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 of DIEs
+ with a DW_AT_specification attribute, because dwarf2_attribute_p()
+ follows this attribute, and therefore might cause us to find a
+ DW_AT_declaration attribute, but that belongs to a different DIE. */
+ return (dwarf2_attribute_true_p (die, DW_AT_declaration, cu)
+ && ! dwarf2_attribute_true_p (die, DW_AT_specification, cu));
}
/* Return the die giving the specification for DIE, if there is
next reply other threads:[~2004-04-15 20:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-15 20:23 Joel Brobecker [this message]
2004-04-16 4:15 ` Jim Blandy
2004-04-16 4:32 ` Joel Brobecker
2004-04-16 14:20 ` Daniel Jacobowitz
2004-04-16 16:18 ` Joel Brobecker
2004-04-16 21:37 ` Jim Blandy
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=20040415202318.GD1564@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