public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "goldstein.w.n at gmail 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: Tue, 03 Jan 2023 19:24:54 +0000 [thread overview]
Message-ID: <bug-29953-131-IJzpYjXoaY@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 #12 from Noah Goldstein <goldstein.w.n at gmail dot com> ---
(In reply to Alexis Engelke from comment #11)
> (In reply to H.J. Lu from comment #4)
> > Try this.
> This fixes the problem, thanks.
>
> (In reply to Noah Goldstein from comment #9)
> > Created attachment 14552 [details]
> > Fix with new API for clamping tunable value
> This also fixes the bug when tunables are enabled, but has the problem that
> no clamping will happen when tunables are disabled.
We can go with H.J's fix, making the tunable setter clamping can be an
independent QOL change later on.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-01-03 19:24 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 [this message]
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
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-IJzpYjXoaY@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).