From: "J. Johnston" <jjohnstn@redhat.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: ia64 prologue skipping patch
Date: Thu, 15 May 2003 21:39:00 -0000 [thread overview]
Message-ID: <3EC408FC.20005@redhat.com> (raw)
In-Reply-To: <1030514235809.ZM10851@localhost.localdomain>
ChangeLog entry modified as asked. Patch checked in. Thanks.
-- Jeff J.
Kevin Buettner wrote:
> On May 14, 7:47pm, J. Johnston wrote:
>
>>Subject: RFA: ia64 prologue skipping patch
>>
>>The attached patch revises the ia64 prologue skipping code. It does a number of
>>things:
>>
>> 1. increases the number of instructions to look at in a prologue
>> 2. allows looking in leaf functions
>> 3. recognizes indirect input register references (one level only)
>> 4. attempts to trust the lim_pc value
>>
>>Number 1 was increased to handle some testsuite cases where the number of
>>parameters was quite high (e.g. 9 parameters). No tuning was involved.
>>
>>Number 4 has the biggest effect. The line table info is more accurate except
>>in the case of optimized code.
>>
>>Ok to commit?
>
>
> Okay (But fix the formatting of your ChangeLog entry - the lines are too
> long.)
>
>
>>2003-05-14 Jeff Johnston <jjohnstn@redhat.com>
>>
>> * ia64-tdep.c: Increase max_skip_non_prologue_insns to 40.
>> (examine_prologue): Support looking through leaf functions, knowing
>> they start with mov r2,r12. Support skipping over indirect stores of the input
>> registers. Upon hitting a non-nop branch instruction or predicated instruction,
>> bail out by setting lim_pc to the current pc value in the loop. At the end,
>> if the lim_pc value is still beyond our calculated value and we have trust_limit set,
>> use the lim_pc value.
>
>
> Kevin
>
prev parent reply other threads:[~2003-05-15 21:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-14 23:47 J. Johnston
2003-05-14 23:58 ` Kevin Buettner
2003-05-15 21:39 ` J. Johnston [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=3EC408FC.20005@redhat.com \
--to=jjohnstn@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@redhat.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