From: Christophe LYON <christophe.lyon@st.com>
To: gdb-patches@sources.redhat.com
Subject: [RFC] Unused variables in testsuite
Date: Fri, 28 Apr 2006 15:01:00 -0000 [thread overview]
Message-ID: <44522E52.9080706@st.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 149 bytes --]
Hi all,
Following my message on the "gdb" list
(http://sources.redhat.com/ml/gdb/2006-04/msg00327.html),
here is the patch I propose.
Christophe.
[-- Attachment #2: patch --]
[-- Type: text/plain, Size: 1426 bytes --]
2006-04-28 Christophe Lyon <christophe.lyon@st.com>
* gdb.cp/m-static.h (class gnu_obj_4): Add dummy member.
* gdb.cp/m-static.cc (main): Write to test4.dummy, so that test4
is allocated by the compiler.
* gdb.mi/var-cmd.c: (do_special_tests): Write to u, anonu, s,
anons, e, anone to force their allocation by the compiler.
Index: gdb.cp/m-static.cc
===================================================================
--- gdb.cp/m-static.cc (revision 96)
+++ gdb.cp/m-static.cc (working copy)
@@ -68,5 +68,6 @@ int main()
gnu_obj_3<long> test3(greek);
gnu_obj_4 test4;
- return 0; // breakpoint: constructs-done
+ test4.dummy = 0;
+ return test4.dummy; // breakpoint: constructs-done
}
Index: gdb.cp/m-static.h
===================================================================
--- gdb.cp/m-static.h (revision 96)
+++ gdb.cp/m-static.h (working copy)
@@ -7,5 +7,8 @@ class gnu_obj_4
static const int nowhere;
// At some point, perhaps:
// static const int everywhere = 317;
+
+ // try to ensure test4 is actually allocated
+ int dummy;
};
Index: gdb.mi/var-cmd.c
===================================================================
--- gdb.mi/var-cmd.c (revision 96)
+++ gdb.mi/var-cmd.c (working copy)
@@ -301,6 +301,12 @@ do_special_tests (void)
int a;
a = 1;
+ u.integer = a;
+ anonu.a = a;
+ s.integer = a;
+ anons.a = a;
+ e = bar;
+ anone = A;
incr_a(2);
}
next reply other threads:[~2006-04-28 15:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-28 15:01 Christophe LYON [this message]
2006-05-02 13:02 ` Christophe LYON
2006-05-05 18:05 ` Daniel Jacobowitz
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=44522E52.9080706@st.com \
--to=christophe.lyon@st.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