From: Tom Tromey <tromey@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>,
Mark Kettenis <mark.kettenis@xs4all.nl>,
gdb-patches@sourceware.org
Subject: Re: [_Complex test 1/4] support_complex_tests in gdb.exp and pass _Complex args to func
Date: Thu, 19 May 2011 17:10:00 -0000 [thread overview]
Message-ID: <m3mxiiboro.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4DD51A55.9000209@codesourcery.com> (Yao Qi's message of "Thu, 19 May 2011 21:25:41 +0800")
>>>>> "Yao" == Yao Qi <yao@codesourcery.com> writes:
Yao> This is a good idea. Done this in new patch.
Thanks for doing this.
Yao> +#ifdef PROTOTYPES
Yao> +void callca (float _Complex f1, float _Complex f2, float _Complex f3)
Yao> +#else
Yao> +callca (f1, f2, f3)
Yao> +float _Complex f1; float _Complex f2; float _Complex f3;
Yao> +#endif
I would not worry about the no PROTOTYPES case. You can leave this in
if you want though.
Yao> +set compile_flags {debug nowarnings quiet}
Yao> +if [support_complex_tests] {
Yao> + set compile_flags "$compile_flags additional_flags=-DTEST_COMPLEX"
I think it is better to use lappend here.
Yao> + gdb_breakpoint callca;
Yao> + gdb_breakpoint callcb;
Yao> + gdb_breakpoint callcc;
Yao> + gdb_breakpoint callcd;
Yao> + gdb_breakpoint callce;
Yao> + gdb_breakpoint callcf;
These ";"s are not needed. There are a few instances of this.
Yao> +# Return a 1 if we should run tests to _Complex types, otherwise, skip it.
Just "Return 1 if...", and then ", otherwise 0.".
I am curious if you tested this in some situation where the complex
tests are skipped.
Tom
next prev parent reply other threads:[~2011-05-19 17:10 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-06 14:13 [patch, testsuite] Tests to _Complex type Yao Qi
2011-05-06 14:33 ` Joseph S. Myers
2011-05-09 2:24 ` Yao Qi
2011-05-09 15:06 ` Tom Tromey
2011-05-19 4:26 ` [_Complex test 1/4] support_complex_tests in gdb.exp and pass _Complex args to func Yao Qi
2011-05-19 8:16 ` Mark Kettenis
2011-05-19 10:16 ` Joseph S. Myers
2011-05-19 13:26 ` Yao Qi
2011-05-19 17:10 ` Tom Tromey [this message]
2011-05-20 8:10 ` Yao Qi
2011-05-26 17:07 ` Tom Tromey
2011-05-30 2:53 ` [committed] " Yao Qi
2011-05-19 13:01 ` Yao Qi
2011-05-19 13:24 ` Mark Kettenis
2011-05-19 13:38 ` Mark Kettenis
2011-05-19 10:12 ` Joseph S. Myers
2011-05-19 4:34 ` [_Complex test 2/4] _Complex type in varargs.exp Yao Qi
2011-05-19 10:13 ` Joseph S. Myers
2011-05-19 13:42 ` Yao Qi
2011-05-19 15:27 ` Joseph S. Myers
2011-05-20 9:09 ` Pedro Alves
2011-05-20 15:22 ` Yao Qi
2011-05-20 15:37 ` Pedro Alves
2011-05-23 4:09 ` Yao Qi
2011-05-23 10:27 ` Pedro Alves
2011-05-30 2:55 ` [committed] " Yao Qi
2011-05-19 17:12 ` Tom Tromey
2011-05-20 8:11 ` Yao Qi
2011-05-19 4:46 ` [_Complex test 3/4] Isolate each test's effect in callfuncs.exp Yao Qi
2011-05-19 18:46 ` Tom Tromey
2011-05-30 2:56 ` [committed] " Yao Qi
2011-05-19 5:09 ` [_Complex test 4/4] _Complex tests " Yao Qi
2011-05-20 8:17 ` Yao Qi
2011-05-24 1:46 ` [_Complex test 4/4 V3] " Yao Qi
2011-05-24 9:00 ` Mark Kettenis
2011-05-24 9:34 ` Yao Qi
2011-05-24 10:00 ` Mark Kettenis
2011-05-24 13:54 ` Yao Qi
2011-05-26 17:07 ` [_Complex test 4/4] " Tom Tromey
2011-05-30 2:57 ` [committed] " Yao Qi
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=m3mxiiboro.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=joseph@codesourcery.com \
--cc=mark.kettenis@xs4all.nl \
--cc=yao@codesourcery.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