From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Wilco Dijkstra <Wilco.Dijkstra@arm.com>,
"Zhangxuelei (Derek)" <zhangxuelei4@huawei.com>,
Szabolcs Nagy <Szabolcs.Nagy@arm.com>,
"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>,
"yikunkero@gmail.com" <yikunkero@gmail.com>
Cc: nd <nd@arm.com>
Subject: Re: [PATCH 2/2] aarch64: Optimized memcpy and memmove for Kunpeng processor
Date: Fri, 18 Oct 2019 15:47:00 -0000 [thread overview]
Message-ID: <62a63744-7513-84fc-0e19-53a2b0690e09@gotplt.org> (raw)
In-Reply-To: <VI1PR0801MB212715FE23D8CE093A7DB152836C0@VI1PR0801MB2127.eurprd08.prod.outlook.com>
On 18/10/19 11:29 am, Wilco Dijkstra wrote:
> Hi Siddhesh,
>
>> The benchtests/scripts/compare_strings.py script dumps a graph png IIRC.
>
> True, but have you seen the output? Try comparing the graphs it generates
> with these: https://www.sourceware.org/ml/libc-alpha/2019-10/msg00563.html
That does look quite neat. As a follow-up to that then, I suggest
either dropping the -g flag from compare_strings.py or putting out a
deprecation warning that plot_strings.py is a better option for
generating graphs and that the -g flag might go away in future.
Siddhesh
next prev parent reply other threads:[~2019-10-18 15:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 13:53 Zhangxuelei (Derek)
2019-10-16 16:20 ` Wilco Dijkstra
2019-10-16 16:25 ` Siddhesh Poyarekar
2019-10-18 15:29 ` Wilco Dijkstra
2019-10-18 15:47 ` Siddhesh Poyarekar [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-11-19 13:34 Zhangxuelei (Derek)
2019-10-17 12:50 Zhangxuelei (Derek)
2019-10-29 15:34 ` Wilco Dijkstra
[not found] ` <8DC571DDDE171B4094D3D33E9685917BD9F88D@DGGEMI529-MBX.china.huawei.com>
2019-10-31 14:04 ` Wilco Dijkstra
2019-10-15 13:26 Wilco Dijkstra
2019-10-14 3:45 Xuelei Zhang
2019-10-15 12:05 ` Szabolcs Nagy
2019-10-16 2:14 ` Yikun Jiang
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=62a63744-7513-84fc-0e19-53a2b0690e09@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=Szabolcs.Nagy@arm.com \
--cc=Wilco.Dijkstra@arm.com \
--cc=libc-alpha@sourceware.org \
--cc=nd@arm.com \
--cc=yikunkero@gmail.com \
--cc=zhangxuelei4@huawei.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).