From: Pedro Alves <palves@redhat.com>
To: Michael Sturm <michael.sturm@intel.com>
Cc: eliz@gnu.org, mark.kettenis@xs4all.nl,
walfred.tedeschi@intel.com, gdb-patches@sourceware.org
Subject: Re: [PATCH v1 1/3] Add AVX512 registers support to GDB.
Date: Fri, 20 Dec 2013 17:29:00 -0000 [thread overview]
Message-ID: <52B47E71.9080803@redhat.com> (raw)
In-Reply-To: <1387533175-4039-2-git-send-email-michael.sturm@intel.com>
Hi there,
I skimmed this (not a real review), and noticed:
> +send_gdb "print have_avx512 ()\r"
> +gdb_expect {
Please use gdb_test_multiple instead of send_gdb/gdb_expect.
> + -re ".. = 1\r\n$gdb_prompt " {
> + pass "check whether processor supports AVX512"
> + }
> + -re ".. = 0\r\n$gdb_prompt " {
Should be a pass too:
pass "check whether processor supports AVX512"
As the test did its job.
> + }
> + -re ".*$gdb_prompt $" {
> + fail "check whether processor supports AVX512"
> + }
> + timeout {
> + fail "check whether processor supports AVX512 (timeout)"
> + }
These last two won't be necessary then.
> +}
> +
This:
> + verbose "processor does not support AVX512; skipping AVX512 tests"
> + return
should probably instead be:
unsupported "processor does not support AVX512; skipping AVX512 tests"
...
> +}
> \ No newline at end of file
Please add one.
--
Pedro Alves
next prev parent reply other threads:[~2013-12-20 17:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-20 9:53 [PATCH v1 0/3] Intel(R) AVX-512 register support Michael Sturm
2013-12-20 9:53 ` [PATCH v1 1/3] Add AVX512 registers support to GDB Michael Sturm
2013-12-20 17:29 ` Pedro Alves [this message]
2014-01-14 9:01 ` Sturm, Michael
2013-12-20 9:53 ` [PATCH v1 3/3] Add AVX512 feature description to GDB manual Michael Sturm
2013-12-20 10:39 ` Eli Zaretskii
2013-12-20 9:53 ` [PATCH v1 2/3] Add AVX512 register support to gdbserver Michael Sturm
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=52B47E71.9080803@redhat.com \
--to=palves@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--cc=michael.sturm@intel.com \
--cc=walfred.tedeschi@intel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).