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 math/28252] Unnecessary memory load in AVX512 SVML codes
Date: Wed, 27 Apr 2022 02:00:27 +0000	[thread overview]
Message-ID: <bug-28252-131-7WZ8NjYoke@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28252-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=28252

--- Comment #3 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The release/2.34/master branch has been updated by Sunil Pandey
<skpgkp2@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=16245986fb9bfe396113fc7dfd1929f69a9e748e

commit 16245986fb9bfe396113fc7dfd1929f69a9e748e
Author: H.J. Lu <hjl.tools@gmail.com>
Date:   Fri Aug 20 06:42:24 2021 -0700

    x86-64: Optimize load of all bits set into ZMM register [BZ #28252]

    Optimize loads of all bits set into ZMM register in AVX512 SVML codes
    by replacing

            vpbroadcastq .L_2il0floatpacket.16(%rip), %zmmX

    and

            vmovups   .L_2il0floatpacket.13(%rip), %zmmX

    with
            vpternlogd $0xff, %zmmX, %zmmX, %zmmX

    This fixes BZ #28252.

    (cherry picked from commit 78c9ec9000f873abe7a15a91b87080a2e4308260)

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-04-27  2:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-20 13:23 [Bug math/28252] New: " hjl.tools at gmail dot com
2021-08-22 13:24 ` [Bug math/28252] " cvs-commit at gcc dot gnu.org
2021-08-22 13:25 ` hjl.tools at gmail dot com
2022-04-27  2:00 ` cvs-commit at gcc dot gnu.org [this message]
2022-05-02 21:30 ` cvs-commit at gcc dot gnu.org

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-28252-131-7WZ8NjYoke@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).