From: Ulrich Weigand <Ulrich.Weigand@de.ibm.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Aditya Kamath1 <Aditya.Kamath1@ibm.com>
Cc: Sangamesh Mallayya <sangamesh.swamy@in.ibm.com>
Subject: Re: [PATCH] Enable-vector-register-visibility-in-core-file-for-AIX.patch
Date: Wed, 15 Mar 2023 18:32:39 +0000 [thread overview]
Message-ID: <1530f842c2d1facadde2ed15ad43ec3015cbf911.camel@de.ibm.com> (raw)
In-Reply-To: <CH2PR15MB35447F4FBE976FD08AF7FB70D6BF9@CH2PR15MB3544.namprd15.prod.outlook.com>
Aditya Kamath1 <Aditya.Kamath1@ibm.com> wrote:
>This is done. Kindly check it out. I have pasted both 64 bit and 32
>bit core file outputs below. It works alright. Thank you for the
>guidance.
This is OK, I've checked the patch in now. Thanks!
>So I always thought rs6000-tdep.c is only used by AIX. Just for my
>knowledge kindly let me know who else is using it? Is it powerpc
>Linux folks? And is the rs600-tdep file is common to both of us.
The rs6000-tdep.c file is used on *all* PowerPC targets (every target
that starts with rs6000- or powerpc*-). This includes AIX and Linux,
but also various BSDs and others.
If you want to find out which tdep file is used for which targets,
you can check the configure.tgt file. You will see the rs6000-tdep.o
file listed in the "gdb_target_obs" variable for all those targets.
Bye,
Ulrich
next prev parent reply other threads:[~2023-03-15 18:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 12:23 Aditya Kamath1
2023-03-13 13:06 ` Ulrich Weigand
2023-03-14 7:43 ` Aditya Kamath1
2023-03-14 17:58 ` Ulrich Weigand
2023-03-15 4:54 ` Aditya Kamath1
2023-03-15 18:32 ` Ulrich Weigand [this message]
2023-03-15 19:04 ` Simon Marchi
2023-03-16 12:50 ` Luis Machado
2023-03-16 13:51 ` Tom Tromey
2023-03-16 15:11 ` 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=1530f842c2d1facadde2ed15ad43ec3015cbf911.camel@de.ibm.com \
--to=ulrich.weigand@de.ibm.com \
--cc=Aditya.Kamath1@ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=sangamesh.swamy@in.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).