From: Yao Qi <qiyaoltc@gmail.com>
To: Nikola Prica <nikola.prica@rt-rk.com>
Cc: pedromfc <pedromfc@linux.vnet.ibm.com>,
Kevin Buettner <kevinb@redhat.com>,
GDB Patches <gdb-patches@sourceware.org>,
"Ananthakrishna Sowda (asowda)" <asowda@cisco.com>,
"Ivan Baev (ibaev)" <ibaev@cisco.com>,
Nemanja Popov <nemanja.popov@rt-rk.com>,
Djordje Todorovic <Djordje.Todorovic@rt-rk.com>,
Ulrich.Weigand@de.ibm.com
Subject: Re: [PING][PATCH] Fix for prologue processing on PowerPC
Date: Tue, 02 Jan 2018 10:29:00 -0000 [thread overview]
Message-ID: <CAH=s-POE68h-bG-UEMxOpkVm0daZVPq8Xnee2ANSqUcCLWAy0w@mail.gmail.com> (raw)
In-Reply-To: <e2997ed1-593e-16a8-7834-139ad8a56c6a@rt-rk.com>
On Tue, Dec 19, 2017 at 3:57 PM, Nikola Prica <nikola.prica@rt-rk.com> wrote:
> Hello Pedro and Kevi,
>
> I've created and tested example based on your example. Thank you for that.
>
gdb.arch/powerpc-prologue-frame.exp is useful, but it is only run on powerpc
target. I personally prefer using gdb unit test or self test to test
powerpc prologue
analyser can stop at the the right instruction after scanning a series of
instructions. See aarch64-tdep.c:aarch64_analyze_prologue_test.
--
Yao (齐尧)
prev parent reply other threads:[~2018-01-02 10:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-22 12:11 Nikola Prica
2017-10-05 2:01 ` Kevin Buettner
2017-10-26 10:02 ` [PING]Fix " Nikola Prica
2017-11-08 16:58 ` Kevin Buettner
2017-11-09 18:15 ` [PING][PATCH] Fix " Nikola Prica
2017-12-01 19:37 ` pedromfc
2017-12-19 15:57 ` Nikola Prica
2017-12-29 18:05 ` Pedro Franco de Carvalho
2018-01-09 11:22 ` Nikola Prica
2018-01-10 17:26 ` Pedro Franco de Carvalho
2018-01-11 15:12 ` Nikola Prica
2018-01-19 7:49 ` Nikola Prica
2018-01-19 19:01 ` Pedro Franco de Carvalho
2018-01-19 19:08 ` Pedro Franco de Carvalho
2018-01-27 14:32 ` Nikola Prica
2018-01-31 18:04 ` Pedro Franco de Carvalho
2018-01-31 18:28 ` Ulrich Weigand
2018-02-01 13:09 ` Nikola Prica
2018-01-02 10:29 ` Yao Qi [this message]
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='CAH=s-POE68h-bG-UEMxOpkVm0daZVPq8Xnee2ANSqUcCLWAy0w@mail.gmail.com' \
--to=qiyaoltc@gmail.com \
--cc=Djordje.Todorovic@rt-rk.com \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=asowda@cisco.com \
--cc=gdb-patches@sourceware.org \
--cc=ibaev@cisco.com \
--cc=kevinb@redhat.com \
--cc=nemanja.popov@rt-rk.com \
--cc=nikola.prica@rt-rk.com \
--cc=pedromfc@linux.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