From: Aditya Kamath1 <Aditya.Kamath1@ibm.com>
To: Aditya Kamath1 via Gdb-patches <gdb-patches@sourceware.org>,
Ulrich Weigand <Ulrich.Weigand@de.ibm.com>
Subject: Re: [PATCH] Modify align-c/align-c++ test case for AIX
Date: Fri, 10 Mar 2023 10:08:29 +0000 [thread overview]
Message-ID: <CH2PR15MB35449149BEC86B561F1C04AED6BA9@CH2PR15MB3544.namprd15.prod.outlook.com> (raw)
In-Reply-To: <CH2PR15MB3544B17CC86D0C8DD7FC4A38D6BA9@CH2PR15MB3544.namprd15.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1445 bytes --]
Hi,
I sent this patch twice by mistake. Kindly ignore this email. I apologise for the same.
From: Gdb-patches <gdb-patches-bounces+aditya.kamath1=ibm.com@sourceware.org> on behalf of Aditya Kamath1 via Gdb-patches <gdb-patches@sourceware.org>
Date: Friday, 10 March 2023 at 2:26 PM
To: Aditya Kamath1 via Gdb-patches <gdb-patches@sourceware.org>, Ulrich Weigand <Ulrich.Weigand@de.ibm.com>
Subject: [EXTERNAL] [PATCH] Modify align-c/align-c++ test case for AIX
Hi all,
Please find attached the patch. {See:- 0001-Modify-align-c-align-c-test-case-for-AIX.patch}
In AIX, we have observed around 1500 failures in align-c/align-c++ testcase. The reason being this testcase shows the alignment outputs of global variables that are unused in the main (). In AIX we need to use atleast one global variable to access the same. This patch is a fix to the same. This issue is like this link pasted in the next line which we fixed before. https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=60204874f5a987b164f7f194d3f96729847fe329
Kindly let me know if this is okay.
Test case command:- gmake RUNTESTFLAGS="gdb.base/align-c.exp" check
gmake RUNTESTFLAGS="gdb.base/align-c++.exp" check
Test case passes before the patch :- 0 for align-c++ and align-c
Test case passes after this patch:- 1134 for align-c++ and 406 for align-c.
Have a nice day ahead.
Thanks and regards,
Aditya.
next prev parent reply other threads:[~2023-03-10 10:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 8:56 Aditya Kamath1
2023-03-10 10:08 ` Aditya Kamath1 [this message]
2023-03-10 8:57 Aditya Kamath1
2023-03-10 14:46 ` Tom Tromey
2023-03-13 13:04 ` Aditya Kamath1
2023-03-13 14:10 ` Ulrich Weigand
2023-03-15 11:52 ` Aditya Kamath1
2023-03-15 12:45 ` Tom Tromey
2023-03-16 7:01 ` Aditya Kamath1
2023-03-17 17:06 ` Ulrich Weigand
2023-03-17 22:03 ` Tom Tromey
2023-03-21 7:01 ` Aditya Kamath1
2023-03-21 7:41 ` Ulrich Weigand
2023-03-21 11:05 ` Pedro Alves
2023-03-21 14:17 ` Tom Tromey
2023-03-21 14:26 ` Ulrich Weigand
2023-03-29 11:28 ` Aditya Kamath1
2023-03-29 13:36 ` Pedro Alves
2023-03-31 12:29 ` Aditya Kamath1
2023-04-04 13:24 ` Aditya Kamath1
2023-04-05 16:33 ` Pedro Alves
2023-04-06 13:15 ` Aditya Kamath1
2023-04-06 16:18 ` Pedro Alves
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=CH2PR15MB35449149BEC86B561F1C04AED6BA9@CH2PR15MB3544.namprd15.prod.outlook.com \
--to=aditya.kamath1@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).