This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH] Don't write beyond destination in __mempcpy_avx512_no_vzeroupper (bug 23196)
- From: Andreas Schwab <schwab at suse dot de>
- To: Florian Weimer <fweimer at redhat dot com>
- Cc: "H.J. Lu" <hjl dot tools at gmail dot com>, Andrew Senkevich <andrew dot n dot senkevich at gmail dot com>, GNU C Library <libc-alpha at sourceware dot org>
- Date: Tue, 22 May 2018 15:21:14 +0200
- Subject: Re: [PATCH] Don't write beyond destination in __mempcpy_avx512_no_vzeroupper (bug 23196)
- References: <mvm1se4romh.fsf@suse.de> <CAMe9rOq_Ba4Hah=Mj9QB1-SkUL1j_TzHjaPVnekiEU4HsacQBg@mail.gmail.com> <mvmpo1nrijw.fsf@suse.de> <3e10ac72-b5a3-f74c-45da-29d8fde75ac7@redhat.com>
On Mai 22 2018, Florian Weimer <fweimer@redhat.com> wrote:
> It has to do with copy sizes and relation to the cache size. I had to
> adjust your reproducer to make it fail on KNL, basically increasing the
> copy size by a factor of 10.
What is the architectural maximum cache size?
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."