From: dje@google.com (Doug Evans)
To: gdb-patches@sourceware.org
Subject: [commit] Update m-static.exp test for optimised -> optimized
Date: Sun, 27 Jun 2010 17:18:00 -0000 [thread overview]
Message-ID: <20100627171809.D14B584613@ruffy.mtv.corp.google.com> (raw)
Hi.
Missed this in earlier patch to fix the spelling of "optimized".
Committed.
2010-06-27 Doug Evans <dje@google.com>
testsuite/
* gdb.cp/m-static.exp: Update expected test output.
Index: gdb.cp/m-static.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.cp/m-static.exp,v
retrieving revision 1.11
diff -u -p -r1.11 m-static.exp
--- gdb.cp/m-static.exp 5 May 2010 18:06:58 -0000 1.11
+++ gdb.cp/m-static.exp 27 Jun 2010 17:16:20 -0000
@@ -123,7 +123,7 @@ gdb_test "print test3.data.value_derived
gdb_test "print test4.elsewhere" "\\$\[0-9\].* = 221" "static const int initialized elsewhere"
# static const int that nobody initializes. From PR gdb/635.
-gdb_test "print test4.nowhere" "field nowhere is nonexistent or has been optimised out" "static const int initialized nowhere"
+gdb_test "print test4.nowhere" "field nowhere is nonexistent or has been optimized out" "static const int initialized nowhere"
# Perhaps at some point test4 should also include a test for a static
# const int that was initialized in the header file. But I'm not sure
reply other threads:[~2010-06-27 17:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20100627171809.D14B584613@ruffy.mtv.corp.google.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).