public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jeevitha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/115242] New: libgcc unwinder does not handle vector registers, even if the target machine supports them.
Date: Mon, 27 May 2024 07:13:58 +0000	[thread overview]
Message-ID: <bug-115242-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115242

            Bug ID: 115242
           Summary: libgcc unwinder does not handle vector registers, even
                    if the target machine supports them.
           Product: gcc
           Version: 15.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libgcc
          Assignee: unassigned at gcc dot gnu.org
          Reporter: jeevitha at gcc dot gnu.org
                CC: bergner at gcc dot gnu.org
  Target Milestone: ---
            Target: powerpc

The powerpc64le-*-linux-gnu target has a baseline of POWER8, so vector support
is always compiled into libgcc_s.so.1.

On powerpc64--linux-gnu and powerpc--linux-gnu, vector support is only present
if GCC is built with a minimum baseline that includes vector support.

In glibc, the test case nptl/tst-thread-exit-clobber fails in BE because of the
above reason. The reason for the failure is explained in detail in the glibc
Bugzilla: https://sourceware.org/bugzilla/show_bug.cgi?id=26566.

             reply	other threads:[~2024-05-27  7:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-27  7:13 jeevitha at gcc dot gnu.org [this message]
2024-05-27  7:14 ` [Bug libgcc/115242] " jeevitha at gcc dot gnu.org
2024-06-25  1:04 ` sjames 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-115242-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).