public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Carl Love <cel@us.ibm.com>
To: gdb-patches@sourceware.org, UlrichWeigand <Ulrich.Weigand@de.ibm.com>
Cc: cel@us.ibm.com
Subject: PowerPC, Fix-test-gdb.base-store.exp
Date: Thu, 12 Oct 2023 07:51:44 -0700	[thread overview]
Message-ID: <6f9c8fa20962129048384d74f6f15d1b37d255ed.camel@us.ibm.com> (raw)

GDB maintainers:

The gdb.base/store.exp test has five failures on PowerPC.  Part of the
issue is the PowerPC DWARF mapping is not correct on Linux.  The first
patch in this series fixes the PowerPC DWARF mapping.  Once the mapping
was fixed another issue was found with how the signal handlers were
handled on PowerPC.  The issue is on PowerPC the sequence of events for
handling signals is a little different on PowerPC from most other
architectures. 

The first patch fixes the PowerPC DWARF register mapping and the signal
handling issue on PowerPC.  These changes fix three of the five
failures on the store.exp test.

The second patch fixes the remaining issue for the store.exp test.  The
remaining issues are due to handling the 128-bit floating point values.
The 64-bit floating point values are stored in the floating point
registers while the 128-bit floating point values are stored in a VSR. 
The DWARF uses the floating point register numbers for both the 64-bit
and 128-bit floating point values.  The second patch adds a routine to
check if a value is a 128-bit floating point value, if so it then
adjusts the register mapping to point to the VSR registers instead of
the 64-bit floating point registers.

The series of two patches have been tested on PowerPC LE and BE.  The
patches have also been tested on Intel X86-64.  No regression failures
was found.

Please let me know if these patches are acceptable for mainline. 
Thanks.

                             Carl 



             reply	other threads:[~2023-10-12 14:51 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-12 14:51 Carl Love [this message]
2023-10-12 14:58 ` [Patch 1/2] " Carl Love
2023-10-13 20:34   ` Keith Seitz
2023-10-13 21:00     ` Carl Love
2023-10-16 11:12       ` Ulrich Weigand
2023-10-16 14:31   ` Andrew Burgess
2023-10-16 15:51     ` Carl Love
2023-10-19 15:54       ` Carl Love
2023-10-24  8:50       ` Andrew Burgess
2023-10-24 16:05         ` Carl Love
2023-10-20 18:08     ` [PATCH 1/2, ver2] " Carl Love
2023-10-24  9:30       ` Andrew Burgess
2023-10-25 13:24         ` Ulrich Weigand
2023-10-30  9:45           ` Andrew Burgess
2023-10-30 16:44             ` Ulrich Weigand
2023-10-30 17:16               ` Carl Love
2023-10-30 17:25               ` [PATCH 1/2, ver3] " Carl Love
2023-11-06 18:24                 ` Carl Love
2023-11-08 10:54                 ` Andrew Burgess
2023-10-12 15:00 ` [PATCH 2/2] " Carl Love
2023-10-13 20:35   ` Keith Seitz
2023-10-13 21:00     ` Carl Love
2023-10-16 11:13       ` Ulrich Weigand
2023-10-16 14:36   ` Andrew Burgess
2023-10-16 15:51     ` Carl Love
2023-10-20 18:08     ` Carl Love
2023-10-24  8:53       ` Andrew Burgess

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=6f9c8fa20962129048384d74f6f15d1b37d255ed.camel@us.ibm.com \
    --to=cel@us.ibm.com \
    --cc=Ulrich.Weigand@de.ibm.com \
    --cc=gdb-patches@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).