From: Carl Love <cel@us.ibm.com>
To: Kevin Buettner <kevinb@redhat.com>, cel@us.ibm.com
Cc: gdb-patches@sourceware.org,
will schmidt <will_schmidt@vnet.ibm.com>,
Pedro Alves <pedro@palves.net>,
Rogerio Alves <rogealve@br.ibm.com>
Subject: RE: [PATCH V3] PowerPC: fix for gdb.base/eh_return.exp
Date: Thu, 12 May 2022 09:00:09 -0700 [thread overview]
Message-ID: <42a431bab647143333a1ea784f528a5d8db3d94f.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?
Good question. I hadn't considered other compilers that might be use.
Guess I am a little to Linux centered. So far, it looks like AIX, xlC
compiler uses -qtable=none, the LLVM compiler uses -mllvm -xcoff-
traceback-table=false, don't know about clang yet. So, looks like the
test is going to need to check for Power, then walk thru the possible
compilers to set the needed option.
Carl
next prev parent reply other threads:[~2022-05-12 16:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 20:07 [PATCH] " Carl Love
2022-05-06 18:08 ` Kevin Buettner
2022-05-06 21:16 ` Pedro Alves
2022-05-06 22:45 ` will schmidt
2022-05-09 19:17 ` [PATCH V2] " Carl Love
2022-05-09 20:57 ` will schmidt
2022-05-10 11:43 ` Pedro Alves
2022-05-11 21:52 ` Carl Love
2022-05-11 21:52 ` [PATCH V3] " Carl Love
2022-05-11 22:48 ` Kevin Buettner
2022-05-12 16:00 ` Carl Love [this message]
2022-06-02 16:52 ` Carl Love
2022-06-08 18:32 ` Pedro Alves
2022-06-08 18:51 ` Carl Love
2022-06-09 15:24 ` Carl Love
2022-06-02 17:00 ` [PATCH V4] " Carl Love
2022-06-07 17:54 ` will schmidt
2022-06-08 15:33 ` [PATCH V5] " Carl Love
2022-06-08 15:36 ` Carl Love
2022-06-08 16:29 ` will schmidt
2022-07-13 17:07 ` [Ping] " Carl Love
2022-07-15 13:41 ` 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=42a431bab647143333a1ea784f528a5d8db3d94f.camel@us.ibm.com \
--to=cel@us.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.com \
--cc=pedro@palves.net \
--cc=rogealve@br.ibm.com \
--cc=will_schmidt@vnet.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).