public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug manual/28766] Document libmvec accuracy
Date: Wed, 19 Jan 2022 15:59:27 +0000 [thread overview]
Message-ID: <bug-28766-131-AU1ZwU6bQh@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28766-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28766
--- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Sunil Pandey <skpgkp2@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=3e63b15d43ea6f61effcf92324e47e981bd7d0a8
commit 3e63b15d43ea6f61effcf92324e47e981bd7d0a8
Author: Sunil K Pandey <skpgkp2@gmail.com>
Date: Tue Jan 18 07:07:44 2022 -0800
x86_64: Document libmvec vector functions accuracy [BZ #28766]
Document maximum 4 ulps accuracy for x86_64 libmvec functions.
This fixes BZ #28766.
Reviewed-By: Paul Zimmermann <Paul.Zimmermann@inria.fr>
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-01-19 15:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 20:33 [Bug manual/28766] New: " hjl.tools at gmail dot com
2022-01-17 21:21 ` [Bug manual/28766] " hjl.tools at gmail dot com
2022-01-19 15:59 ` cvs-commit at gcc dot gnu.org [this message]
2022-01-19 16:01 ` hjl.tools at gmail 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-28766-131-AU1ZwU6bQh@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).