From: Wu Zhou <woodzltc@cn.ibm.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Ramana Radhakrishnan <ramana.radhakrishnan@codito.com>,
gdb@sourceware.org
Subject: Re: a question about rs6k's prologue analysis
Date: Thu, 12 Oct 2006 03:59:00 -0000 [thread overview]
Message-ID: <452DBDA0.6070202@cn.ibm.com> (raw)
In-Reply-To: <20061011162208.GX1065@adacore.com>
Joel Brobecker wrote:
>> I knew this sounded familiar. Here it is:
>
> Yes, me too! :-)
>
>> http://sourceware.org/ml/gdb-patches/2004-12/msg00234.html
>> http://sourceware.org/ml/gdb-patches/2005-06/msg00242.html
>>
>> Joel, things have changed a lot since then - if you have a chance to
>> respond to my last message there, I'll take another look at it.
>
> For the record:
>
> http://www.sourceware.org/ml/gdb-patches/2006-10/msg00119.html
>
I had a test with your patch, changing the blrl test to be additional. It works ok in my scenario.
But I don't do any regression test yet (will do that later, having other things for rush). Also
that I am now applying your patch to RHEL4's gdb sources (It seems that community gdb has some
problems on ppc64, which hinders our scenario.). I will apply that patch to community source later
to see if there are any regression.
BTW, adapting the first three instructions to be four don't work in some cases. I see some cases
where bl_to_blrl occurs at about the 6th or even 8th instruction of the prologue.
Thanks a lot for all your help. I will return back to regression test a while later.
Regards
- Wu Zhou
next prev parent reply other threads:[~2006-10-12 3:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 10:13 Wu Zhou
2006-10-11 10:47 ` Ramana Radhakrishnan
2006-10-11 13:53 ` Daniel Jacobowitz
2006-10-11 16:22 ` Joel Brobecker
2006-10-12 3:59 ` Wu Zhou [this message]
2006-10-13 4:13 ` Wu Zhou
2006-10-13 19:09 ` Michael Snyder
2006-10-13 22:03 ` Daniel Jacobowitz
2006-10-14 15:18 ` Wu Zhou
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=452DBDA0.6070202@cn.ibm.com \
--to=woodzltc@cn.ibm.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=ramana.radhakrishnan@codito.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