From: Carl Love via Gdb-patches <gdb-patches@sourceware.org>
To: Kevin Buettner <kevinb@redhat.com>
Cc: Rogerio Alves <rogealve@br.ibm.com>,
Pedro Alves <pedro@palves.net>,
gdb-patches@sourceware.org
Subject: RE: [PATCH V3] PowerPC: fix for gdb.base/eh_return.exp
Date: Thu, 02 Jun 2022 09:52:53 -0700 [thread overview]
Message-ID: <fef7684a0035e95f0ca2c99cac923ddce11257c0.camel@us.ibm.com> (raw)
In-Reply-To: <20220511154822.3b9f7d74@f35-zws-1>
Kevin:
On Wed, 2022-05-11 at 15:48 -0700, Kevin Buettner wrote:
> On Wed, 11 May 2022 14:52:32 -0700
> Carl Love <cel@us.ibm.com> wrote:
>
> > + # Disable the Traceback Table generation, using the PowerPC
> > specific
> > + # gcc option, so the test gdb_test_multiple "disassemble eh2"
> > will match
>
> What happens when some compiler other than gcc is used to run the
> test?
I updated the patch to set the compiler options for gcc and XLC. The
test was run on AIX and passes with the patch. Note that AIX actually
uses gcc to compile gdb. We tried compiling gdb with the xlc compiler.
We ran into other gdb compilation errors that we were not able to
resolve. We were able to verify that the xlc options to disable the
Traceback Buffer were right but that was it.
If other compilers are used to compile gdb on power, the option for
that compiler to disable the Traceback Table will need to be added to
the test otherwise the test will fail for that compiler.
I will post the updated version of the patch.
Carl
next prev parent reply other threads:[~2022-06-02 16:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 20:07 [PATCH] " Carl Love via Gdb-patches
2022-05-06 18:08 ` Kevin Buettner via Gdb-patches
2022-05-06 21:16 ` Pedro Alves
2022-05-06 22:45 ` will schmidt via Gdb-patches
2022-05-09 19:17 ` [PATCH V2] " Carl Love via Gdb-patches
2022-05-09 20:57 ` will schmidt via Gdb-patches
2022-05-10 11:43 ` Pedro Alves
2022-05-11 21:52 ` Carl Love via Gdb-patches
2022-05-11 21:52 ` [PATCH V3] " Carl Love via Gdb-patches
2022-05-11 22:48 ` Kevin Buettner via Gdb-patches
2022-05-12 16:00 ` Carl Love via Gdb-patches
2022-06-02 16:52 ` Carl Love via Gdb-patches [this message]
2022-06-08 18:32 ` Pedro Alves
2022-06-08 18:51 ` Carl Love via Gdb-patches
2022-06-09 15:24 ` Carl Love via Gdb-patches
2022-06-02 17:00 ` [PATCH V4] " Carl Love via Gdb-patches
2022-06-07 17:54 ` will schmidt via Gdb-patches
2022-06-08 15:33 ` [PATCH V5] " Carl Love via Gdb-patches
2022-06-08 15:36 ` Carl Love via Gdb-patches
2022-06-08 16:29 ` will schmidt via Gdb-patches
2022-07-13 17:07 ` [Ping] " Carl Love via Gdb-patches
2022-07-15 13:41 ` Ulrich Weigand via Gdb-patches
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=fef7684a0035e95f0ca2c99cac923ddce11257c0.camel@us.ibm.com \
--to=gdb-patches@sourceware.org \
--cc=cel@us.ibm.com \
--cc=kevinb@redhat.com \
--cc=pedro@palves.net \
--cc=rogealve@br.ibm.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