From: Michael Snyder <msnyder@vmware.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: [RFA] gdb.cp/overload.cc: add cast to prevent compiler warning
Date: Sun, 27 Feb 2011 21:16:00 -0000 [thread overview]
Message-ID: <4D6ABBFF.5030401@vmware.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 64 bytes --]
The compiler warning prevents this test from actually running.
[-- Attachment #2: overload.txt --]
[-- Type: text/plain, Size: 630 bytes --]
2011-02-27 Michael Snyder <msnyder@vmware.com>
* gdb.cp/overload.cc: Add cast to prevent compiler warning.
Index: gdb.cp/overload.cc
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.cp/overload.cc,v
retrieving revision 1.7
diff -u -p -u -p -r1.7 overload.cc
--- gdb.cp/overload.cc 4 Nov 2010 20:43:25 -0000 1.7
+++ gdb.cp/overload.cc 27 Feb 2011 21:00:47 -0000
@@ -110,7 +110,7 @@ int main ()
unsigned long arg10 =10;
float arg11 =100.0;
double arg12 = 200.0;
- int arg13 = 200.0;
+ int arg13 = (int) 200.0;
char arg14 = 'a';
A a;
next reply other threads:[~2011-02-27 21:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-27 21:16 Michael Snyder [this message]
2011-02-28 5:08 ` Joel Brobecker
2011-02-28 18:03 ` Michael Snyder
2011-02-28 18:17 ` Tom Tromey
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=4D6ABBFF.5030401@vmware.com \
--to=msnyder@vmware.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