From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: hjl.tools@gmail.com
Cc: gdb-patches@sourceware.org
Subject: Re: PING PATCH: Update x86 stack align analyzer
Date: Wed, 06 Aug 2008 18:04:00 -0000 [thread overview]
Message-ID: <200808061803.m76I3geR020710@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <6dc9ffc80808061007o7f35f10etbd136be66ab91380@mail.gmail.com> (hjl.tools@gmail.com)
> Date: Wed, 6 Aug 2008 10:07:06 -0700
> From: "H.J. Lu" <hjl.tools@gmail.com>
>
> PING.
I'll try to look at it tonight.
> H.J.
> On Wed, Jul 30, 2008 at 2:11 PM, H.J. Lu <hongjiu.lu@intel.com> wrote:
> > Gcc 4.4 revision 138335:
> >
> > http://gcc.gnu.org/ml/gcc-cvs/2008-07/msg01048.html
> >
> > introduced new ways to align stack. This patch teaches gdb how to
> > recognize the new stack prologue. OK for trunk?
> >
> > Please CC me since I am not on the gdb-patches mailing list.
> >
> > Thanks.
> >
> >
> > H.J.
> > ----
> > 2008-07-30 Xuepeng Guo <xuepeng.guo@intel.com>
> > H.J. Lu <hongjiu.lu@intel.com>
> >
> > * amd64-tdep.c (amd64_frame_cache): Add saved_sp_reg.
> > (amd64_init_frame_cache): Initialize saved_sp_reg.
> > (amd64_analyze_stack_align): New.
> > (amd64_analyze_prologue): Call it.
> > (amd64_frame_cache): Try to use saved_sp_reg if frame is invalid.
> >
> > * amd64-tdep.h (amd64_regnum): Add AMD64_R9_REGNUM to
> > AMD64_R14_REGNUM.
> >
> > * i386-tdep.c (i386_frame_cache): Remove stack_align. Add
> > saved_sp_reg.
> > (i386_alloc_frame_cache): Remove stack_align. Initialize
> > saved_sp_reg to I386_ESP_REGNUM.
> > (i386_analyze_stack_align): Rewrite.
> > (i386_frame_cache): Use saved_sp_reg only if frame is invalid.
> >
>
prev parent reply other threads:[~2008-08-06 18:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 17:08 H.J. Lu
2008-08-06 18:04 ` Mark Kettenis [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=200808061803.m76I3geR020710@brahms.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb-patches@sourceware.org \
--cc=hjl.tools@gmail.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