public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Florian Weimer <fweimer@redhat.com>
Cc: "H.J. Lu" <hjl.tools@gmail.com>,
	 Andrew Senkevich <andrew.n.senkevich@gmail.com>,
	 GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] Don't write beyond destination in __mempcpy_avx512_no_vzeroupper (bug 23196)
Date: Tue, 22 May 2018 14:12:00 -0000	[thread overview]
Message-ID: <mvmvabfpyo9.fsf@suse.de> (raw)
In-Reply-To: <0d694123-e9f9-9d4d-6ad0-71a6ff0fd44a@redhat.com> (Florian Weimer's message of "Tue, 22 May 2018 15:53:29 +0200")

On Mai 22 2018, Florian Weimer <fweimer@redhat.com> wrote:

> My test machine had an L2 cache size of 1 MiB.

Then you should be safe, a 64K mempcpy is enough to trigger it.

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."

  reply	other threads:[~2018-05-22 14:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-22 10:06 Andreas Schwab
2018-05-22 11:59 ` H.J. Lu
2018-05-22 12:20   ` Andreas Schwab
2018-05-22 12:27     ` H.J. Lu
2018-05-22 12:47       ` Andreas Schwab
2018-05-22 12:56         ` H.J. Lu
2018-05-22 13:06           ` Andreas Schwab
2018-05-22 12:56     ` Florian Weimer
2018-05-22 13:21       ` Andreas Schwab
2018-05-22 13:53         ` Florian Weimer
2018-05-22 14:12           ` Andreas Schwab [this message]
2018-05-22 14:36             ` Florian Weimer
2018-05-22 15:06               ` Andreas Schwab
2018-05-22 15:35                 ` Florian Weimer
2018-05-22 15:38                   ` Andreas Schwab
2018-05-22 16:33                     ` H.J. Lu
2018-05-23  7:55                       ` Andreas Schwab

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=mvmvabfpyo9.fsf@suse.de \
    --to=schwab@suse.de \
    --cc=andrew.n.senkevich@gmail.com \
    --cc=fweimer@redhat.com \
    --cc=hjl.tools@gmail.com \
    --cc=libc-alpha@sourceware.org \
    /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).