From: Mark Kettenis <kettenis@chello.nl>
To: gdb-patches@sources.redhat.com, brobecker@gnat.com
Subject: [PATCH/RFC] observer tests & GCC 3.4
Date: Thu, 11 Dec 2003 13:55:00 -0000 [thread overview]
Message-ID: <200312111355.hBBDtFE7000504@elgar.kettenis.dyndns.org> (raw)
The compiler is getting too smart for its own good again. At the end
of observer.c, we have a bit of code that used in the
gdb.gdb/observer.exp testcase. Since the variables and functions are
declared static, the compiler simply optimizes these out. The
attached patch fixes this. Objections?
Mark
Index: ChangeLog
from Mark Kettenis <kettenis@gnu.org>
* observer.c (observer_test_first_observer,
observer_test_second_observer, observer_test_third_observer):
Don't define as `static'.
(observer_test_first_notification_function,
observer_test_second_notification_function,
observer_test_third_notification_function): Likewise.
Index: observer.c
===================================================================
RCS file: /cvs/src/src/gdb/observer.c,v
retrieving revision 1.3
diff -u -p -r1.3 observer.c
--- observer.c 18 Mar 2003 18:05:50 -0000 1.3
+++ observer.c 11 Dec 2003 13:52:40 -0000
@@ -191,30 +191,30 @@ observer_notify_normal_stop (void)
generic_observer_notify (normal_stop_subject, NULL);
}
-/* The following code is only used to unit-test the observers from
- our testsuite. DO NOT USE IT within observer.c! */
+/* The following code is only used to unit-test the observers from our
+ testsuite. DO NOT USE IT within observer.c (or anywhere else for
+ that matter)! */
-/* Since this code will not be used within GDB, it will trigger
- a warning if we decide to compile with -Wunused-function.
- This is ok for now. (brobecker 2003-03-18) */
+/* If we define these variables and functions as `static', the
+ compiler will optimize them out. */
-static int observer_test_first_observer = 0;
-static int observer_test_second_observer = 0;
-static int observer_test_third_observer = 0;
+int observer_test_first_observer = 0;
+int observer_test_second_observer = 0;
+int observer_test_third_observer = 0;
-static void
+void
observer_test_first_notification_function (void)
{
observer_test_first_observer++;
}
-static void
+void
observer_test_second_notification_function (void)
{
observer_test_second_observer++;
}
-static void
+void
observer_test_third_notification_function (void)
{
observer_test_third_observer++;
next reply other threads:[~2003-12-11 13:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-11 13:55 Mark Kettenis [this message]
2003-12-11 14:14 ` Joel Brobecker
2003-12-11 14:24 ` Daniel Jacobowitz
2003-12-11 14:34 ` Eli Zaretskii
2003-12-12 16:24 ` Mark Kettenis
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=200312111355.hBBDtFE7000504@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=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