public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tuliom at ascii dot art.br" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/25905] VSX registers are corrupted during PLT resolution when glibc is built with --disable-multi-arch and --with-cpu=power9
Date: Tue, 12 May 2020 19:24:57 +0000	[thread overview]
Message-ID: <bug-25905-131-fzpPKpgu6X@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25905-131@http.sourceware.org/bugzilla/>

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

Tulio Magno Quites Machado Filho <tuliom at ascii dot art.br> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED

--- Comment #4 from Tulio Magno Quites Machado Filho <tuliom at ascii dot art.br> ---
As mentioned in the previous comment, this issue has been fixed with:

commit 4a4db1de2f0fd936b583698dcc1b1c12a71828c8
Author: Paul E. Murphy <murphyp@linux.vnet.ibm.com>
Date:   Fri May 1 14:30:42 2020 -0500

    powerpc64le/power9: guard power9 strcmp against rtld usage [BZ# 25905]

    strcmp is used while resolving PLT references.  Vector registers
    should not be used during this.  The P9 strcmp makes heavy use of
    vector registers, so it should be avoided in rtld.

    This prevents quiet vector register corruption when glibc is configured
    with --disable-multi-arch and --with-cpu=power9.  This can be seen with
    test-float64x-compat_totalordermag during the first call into
    totalordermagf64x@GLIBC_2.27.

    Add a guard to fallback to the power8 implementation when building
    power9 strcmp for libraries other than libc.

    Reviewed-by: Adhemerval Zanella  <adhemerval.zanella@linaro.org>

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

      parent reply	other threads:[~2020-05-12 19:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-01 19:40 [Bug dynamic-link/25905] New: " murphyp at linux dot vnet.ibm.com
2020-05-01 19:41 ` [Bug dynamic-link/25905] " murphyp at linux dot vnet.ibm.com
2020-05-01 19:43 ` murphyp at linux dot vnet.ibm.com
2020-05-05 19:34 ` tuliom at ascii dot art.br
2020-05-06 22:20 ` murphyp at linux dot vnet.ibm.com
2020-05-06 22:20 ` murphyp at linux dot vnet.ibm.com
2020-05-12 19:24 ` tuliom at ascii dot art.br [this message]

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-25905-131-fzpPKpgu6X@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).