Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Aditya Kamath <Aditya.Kamath1@ibm.com>
To: Simon Marchi <simon.marchi@polymtl.ca>,
	Ulrich Weigand <Ulrich.Weigand@de.ibm.com>,
	Aditya Vidyadhar Kamath <akamath996@gmail.com>,
	"tom@tromey.com" <tom@tromey.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	SANGAMESH MALLAYYA <sangamesh.swamy@in.ibm.com>
Subject: RE: [PATCH v5 1/4] Remove stale legacy code from rs6000-aix-nat.c file.
Date: Wed, 14 Oct 2026 09:15:28 +0000	[thread overview]
Message-ID: <DSWPR15MB3198172F6E0E5D22B57AB8E8E1D69D2@DSWPR15MB319817.namprd15.prod.outlook.com> (raw)
In-Reply-To: <56645038-9b78-447a-aa34-976019f626e0@polymtl.ca>

[-- Attachment #1: Type: text/plain, Size: 1499 bytes --]


Hi Simon,

>Thanks for digging into the pipe issue, it is indeed reproducible on
>Linux.  Please see this small 2-patch series that hopefully fixes it for
>you too and makes testing less noisy

>https://urldefense.proofpoint.com/v2/url?u=https-3A__inbox.sourceware.org_gdb-2Dpatches_20261013171340.1748775-2D1-2Dsimon.marchi-40efficios.com_T_-23m50cf93bf2bbe1a9fd9c7ac7237519570df8a5ceb&d=DwICaQ&c=BSDicqBQBDjDI9RkVyTcHQ&r=f-oUQ8ByG1nZ71OI9p76qywCPh7mxzU69hBYnkP9Nis&m=a00eP242E_D4VAASU_j8zMu2t_Vf29AIAghQEZll_XzeU_APW-TVoCat0riBcaj3&s=82cvPgaYrtuANiE_ZnSQXU71WChpKrAdgNMXzRKKCwg&e=

Thanks for the patch.

I re-ran the full gdb.base testsuite in 32-bit mode with your
patches applied.  Here are the 32-bit numbers from before my series,
after my series, and after my series plus your patches:

                          32-bit
                                    before   after    after + your patches
  expected passes             41687   41541    41640
  unexpected failures         2302    2294     2308
  unexpected successes           1       1        1
  expected failures                     15      15       15
  known failures                   30      30       30
  unresolved testcases            11      86       11
  untested testcases           107     107      108
  unsupported tests             179     179      178


Will give more information in that patch thread.

Have a nice day ahead.

Regards,
Aditya.

[-- Attachment #2: Type: text/html, Size: 6118 bytes --]

  reply	other threads:[~2026-10-14  9:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-13 11:19 Aditya Vidyadhar Kamath
2026-10-13 11:19 ` [PATCH v5 2/4] Remove obsolete getthrds and HAVE_PTRACE64 configure checks Aditya Vidyadhar Kamath
2026-10-13 11:19 ` [PATCH v5 3/4] Modernise aix-thread.c by combining ptrace wrappers Aditya Vidyadhar Kamath
2026-10-13 11:19 ` [PATCH v5 4/4] Fix 32-bit GPR and SPR register reads/writes in pthdb callbacks Aditya Vidyadhar Kamath
2026-10-13 12:00 ` [PATCH v5 1/4] Remove stale legacy code from rs6000-aix-nat.c file Ulrich Weigand
2026-10-13 12:55   ` Aditya Kamath
2026-10-13 13:31     ` Ulrich Weigand
2026-10-13 17:16       ` Simon Marchi
2026-10-14  9:15         ` Aditya Kamath [this message]
2026-10-14 10:44           ` Ulrich Weigand
2026-10-15 13:38             ` Aditya Kamath
2026-10-15 14:37               ` Ulrich Weigand

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=DSWPR15MB3198172F6E0E5D22B57AB8E8E1D69D2@DSWPR15MB319817.namprd15.prod.outlook.com \
    --to=aditya.kamath1@ibm.com \
    --cc=Ulrich.Weigand@de.ibm.com \
    --cc=akamath996@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sangamesh.swamy@in.ibm.com \
    --cc=simon.marchi@polymtl.ca \
    --cc=tom@tromey.com \
    /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