public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/29953] Invalid x86_non_temporal_threshold without cache info
Date: Mon, 13 Mar 2023 18:00:45 +0000 [thread overview]
Message-ID: <bug-29953-131-DSatBEQRQU@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29953-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29953
--- Comment #15 from Florian Weimer <fweimer at redhat dot com> ---
(In reply to cvs-commit@gcc.gnu.org from comment #13)
> The master branch has been updated by H.J. Lu <hjl@sourceware.org>:
>
> https://sourceware.org/git/gitweb.cgi?p=glibc.git;
> h=48b74865c63840b288bd85b4d8743533b73b339b
>
> commit 48b74865c63840b288bd85b4d8743533b73b339b
> Author: H.J. Lu <hjl.tools@gmail.com>
> Date: Tue Jan 3 13:06:48 2023 -0800
>
> x86: Check minimum/maximum of non_temporal_threshold [BZ #29953]
>
> The minimum non_temporal_threshold is 0x4040. non_temporal_threshold may
> be set to less than the minimum value when the shared cache size isn't
> available (e.g., in an emulator) or by the tunable. Add checks for
> minimum and maximum of non_temporal_threshold.
>
> This fixes BZ #29953.
H.J., do you intend to backport this? Can we close this bug?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-03-13 18:00 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-02 17:33 [Bug dynamic-link/29953] New: " engelke at in dot tum.de
2023-01-02 21:21 ` [Bug dynamic-link/29953] " goldstein.w.n at gmail dot com
2023-01-03 0:05 ` goldstein.w.n at gmail dot com
2023-01-03 12:49 ` engelke at in dot tum.de
2023-01-03 16:23 ` hjl.tools at gmail dot com
2023-01-03 17:52 ` goldstein.w.n at gmail dot com
2023-01-03 17:55 ` hjl.tools at gmail dot com
2023-01-03 18:00 ` goldstein.w.n at gmail dot com
2023-01-03 18:04 ` hjl.tools at gmail dot com
2023-01-03 18:13 ` goldstein.w.n at gmail dot com
2023-01-03 18:22 ` hjl.tools at gmail dot com
2023-01-03 18:39 ` engelke at in dot tum.de
2023-01-03 19:24 ` goldstein.w.n at gmail dot com
2023-01-03 21:58 ` cvs-commit at gcc dot gnu.org
2023-01-25 21:05 ` decui at microsoft dot com
2023-03-13 17:59 ` fweimer at redhat dot com
2023-03-13 18:00 ` fweimer at redhat dot com
2023-03-13 18:00 ` fweimer at redhat dot com [this message]
2023-03-13 18:17 ` hjl.tools at gmail dot com
2023-03-15 22:18 ` cvs-commit at gcc dot gnu.org
2023-04-20 15:52 ` cvs-commit at gcc dot gnu.org
2023-04-20 15:53 ` cvs-commit at gcc dot gnu.org
2023-05-08 16:44 ` fw at deneb dot enyo.de
2023-05-08 17:09 ` fweimer at redhat dot com
2023-05-08 17:09 ` fweimer at redhat dot com
2023-07-17 7:29 ` fweimer at redhat dot com
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=bug-29953-131-DSatBEQRQU@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).