Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: brobecker@adacore.com
Cc: gdb-patches@sourceware.org
Subject: Re: PING: [RFA/i386] 2 more patterns in i386_analyze_stack_align
Date: Sun, 31 Dec 2006 12:15:00 -0000	[thread overview]
Message-ID: <200612311215.kBVCF75Z010607@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <20061231060844.GP3640@adacore.com> (message from Joel Brobecker 	on Sun, 31 Dec 2006 10:08:44 +0400)

> Date: Sun, 31 Dec 2006 10:08:44 +0400
> From: Joel Brobecker <brobecker@adacore.com>
> 
> Ping?
> 
> No rush. I just read a message from Mark saying that he was losing
> messages, so I'm resending this message, JIC.

Probably a good idea ;).

> > Index: i386-tdep.c
> > ===================================================================
> > RCS file: /cvs/src/src/gdb/i386-tdep.c,v
> > retrieving revision 1.225
> > diff -u -p -r1.225 i386-tdep.c
> > --- i386-tdep.c	8 Aug 2006 21:36:46 -0000	1.225
> > +++ i386-tdep.c	20 Dec 2006 10:21:58 -0000
> > @@ -497,15 +497,27 @@ static CORE_ADDR
> >  i386_analyze_stack_align (CORE_ADDR pc, CORE_ADDR current_pc,
> >  			  struct i386_frame_cache *cache)
> >  {
> > -  static const gdb_byte insns[10] = { 
> > +  static const gdb_byte insns_ecx[10] = { 
> >      0x8d, 0x4c, 0x24, 0x04,	/* leal  4(%esp), %ecx */
> >      0x83, 0xe4, 0xf0,		/* andl  $-16, %esp */
> >      0xff, 0x71, 0xfc		/* pushl -4(%ecx) */
> >    };
> > +  static const gdb_byte insns_edx[10] = { 
> > +    0x8d, 0x54, 0x24, 0x04,	/* leal  4(%esp), %edx */
> > +    0x83, 0xe4, 0xf0,		/* andl  $-16, %esp */
> > +    0xff, 0x72, 0xfc		/* pushl -4(%edx) */
> > +  };
> > +  static const gdb_byte insns_eax[10] = { 
> > +    0x8d, 0x44, 0x24, 0x04,	/* leal  4(%esp), %eax */
> > +    0x83, 0xe4, 0xf0,		/* andl  $-16, %esp */
> > +    0xff, 0x70, 0xfc		/* pushl -4(%eax) */
> > +  };
> >    gdb_byte buf[10];

Hmm, you're missing the %ebx case here.  Now on ELF systems, you'll
probably never see it since %ebx is used for GOT access, but on other
object formats I don't think there is any reason why GCC wouldn't
choose to use %ebx as well.

This looks reasonable otherwise, except that I would sort the patterns
in a more logical order.

Mark


  reply	other threads:[~2006-12-31 12:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-20 10:49 Joel Brobecker
2006-12-31  6:08 ` PING: " Joel Brobecker
2006-12-31 12:15   ` Mark Kettenis [this message]
2006-12-31 14:39     ` Joel Brobecker
2007-01-05  6:48     ` Joel Brobecker
2007-01-05 11:05       ` Mark Kettenis
2007-01-05 14:36         ` Joel Brobecker
2007-01-05 14:58           ` Mark Kettenis
2007-01-05 16:42             ` Joel Brobecker

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=200612311215.kBVCF75Z010607@brahms.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /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