Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Carl Love via Gdb-patches <gdb-patches@sourceware.org>
To: Pedro Alves <pedro@palves.net>, Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: RE: [PATCH V3] PowerPC: fix for gdb.base/eh_return.exp
Date: Wed, 08 Jun 2022 11:51:44 -0700	[thread overview]
Message-ID: <991220323670a033af39dcc64255567c216034aa.camel@us.ibm.com> (raw)
In-Reply-To: <d913587c-c521-23f9-6354-2a3bc209b1fb@palves.net>

Pedro:

On Wed, 2022-06-08 at 19:32 +0100, Pedro Alves wrote:
> 
> The compiler used to build gdb does not have to be the same used to
> run tests.  You can build gdb with gcc as usual, and then run tests
> with some other compiler, like:
> 
>  $ make check RUNTESTFLAGS="CC_FOR_TARGET=foo CXX_FOR_TARGET=foo++"
> 

OK, I wasn't aware of that.  

I sent email to my contact in AIX to see if they can try that for me. 
Unfortunately, I wasn't able to get gdb compiled on AIX so the testing
of the patch was done my a person in the AIX team who is able to build
gdb on AIX with gcc.  Hopefully they will be able to do some more
testing for me.

                     Carl 


  reply	other threads:[~2022-06-08 18:52 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
2022-06-08 18:32                 ` Pedro Alves
2022-06-08 18:51                   ` Carl Love via Gdb-patches [this message]
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=991220323670a033af39dcc64255567c216034aa.camel@us.ibm.com \
    --to=gdb-patches@sourceware.org \
    --cc=cel@us.ibm.com \
    --cc=kevinb@redhat.com \
    --cc=pedro@palves.net \
    /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