From: Doug Evans <dje@google.com>
To: Andrew Pinski <pinskia@gmail.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [COMMITTED PATCH] Fix clang compilation errors in gdb.mi/basics.c
Date: Mon, 25 Aug 2014 21:57:00 -0000 [thread overview]
Message-ID: <CADPb22TZyR_68WxgOpgqXo_i88XbNMF1b-wPi6vehLf-xDtSyw@mail.gmail.com> (raw)
In-Reply-To: <CA+=Sn1=5iyT0d_8BWfVkh-nCMGcFABDe3vQ7QfuMdsBHyd=oDQ@mail.gmail.com>
On Mon, Aug 25, 2014 at 2:39 PM, Andrew Pinski <pinskia@gmail.com> wrote:
> On Mon, Aug 25, 2014 at 12:44 PM, Doug Evans <dje@google.com> wrote:
>> Hi.
>>
>> This patch gets a few more tests working with clang.
>
>
> Seems like maybe we should be compiling with -w for clang instead of
> trying to change the testcase itself. Because now we don't know if
> the change to the testcase changed the behavior it was testing or not.
>
> Thanks,
> Andrew
I thought of that.
In this case it would be really unfortunate if a test was relying on
things that this particular patch changes.
In other situations I'm sure I would agree with you.
I didn't do an exhaustive search for what might change, granted, but
OTOH the search was non-minimal.
>
>>
>> gdb compile failed, ../../../binutils-gdb/gdb/testsuite/gdb.mi/basics.c:32:1: warning: type
>> specifier missing, defaults to 'int' [-Wimplicit-int]
>> callee3 (char *strarg)
>> ^
>> ../../../binutils-gdb/gdb/testsuite/gdb.mi/basics.c:35:1: warning: control
>> reaches end of non-void function [-Wreturn-type]
>> }
>> ^
>> ...
>>
>> 2014-08-25 Doug Evans <dje@google.com>
>>
>> * gdb.mi/basics.c (callee3, callee2, callee1): Specify result type.
>> (main): Ditto.
>>
>> diff --git a/gdb/testsuite/gdb.mi/basics.c b/gdb/testsuite/gdb.mi/basics.c
>> index 0a4f9de..0eabcd1 100644
>> --- a/gdb/testsuite/gdb.mi/basics.c
>> +++ b/gdb/testsuite/gdb.mi/basics.c
>> @@ -29,17 +29,17 @@ int callee4 (void)
>> C = A + B;
>> return 0;
>> }
>> -callee3 (char *strarg)
>> +void callee3 (char *strarg)
>> {
>> callee4 ();
>> }
>>
>> -callee2 (int intarg, char *strarg)
>> +void callee2 (int intarg, char *strarg)
>> {
>> callee3 (strarg);
>> }
>>
>> -callee1 (int intarg, char *strarg, double fltarg)
>> +void callee1 (int intarg, char *strarg, double fltarg)
>> {
>> callee2 (intarg, strarg);
>> }
>> @@ -57,7 +57,7 @@ void do_nothing (void)
>> {
>> }
>>
>> -main ()
>> +int main ()
>> {
>> callee1 (2, "A string argument.", 3.5);
>> callee1 (2, "A string argument.", 3.5);
prev parent reply other threads:[~2014-08-25 21:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-25 19:44 Doug Evans
2014-08-25 21:39 ` Andrew Pinski
2014-08-25 21:57 ` Doug Evans [this message]
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=CADPb22TZyR_68WxgOpgqXo_i88XbNMF1b-wPi6vehLf-xDtSyw@mail.gmail.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=pinskia@gmail.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