This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: [Fastboot] Re: [-mm patch] i386: enable REGPARM by default
- From: Daniel Jacobowitz <dan at debian dot org>
- To: Vivek Goyal <vgoyal at in dot ibm dot com>
- Cc: Andrew Morton <akpm at osdl dot org>, Adrian Bunk <bunk at stusta dot de>,fastboot at lists dot osdl dot org, linux-kernel at vger dot kernel dot org,gdb at sources dot redhat dot com
- Date: Mon, 27 Jun 2005 10:00:29 -0400
- Subject: Re: [Fastboot] Re: [-mm patch] i386: enable REGPARM by default
- References: <20050624200916.GJ6656@stusta.de> <20050624132826.4cdfb63c.akpm@osdl.org> <20050627132941.GD3764@in.ibm.com>
On Mon, Jun 27, 2005 at 06:59:41PM +0530, Vivek Goyal wrote:
> On Fri, Jun 24, 2005 at 01:28:26PM -0700, Andrew Morton wrote:
> > Adrian Bunk <bunk@stusta.de> wrote:
> > >
> > > This patch:
> > > - removes the dependency of REGPARM on EXPERIMENTAL
> > > - let REGPARM default to y
> >
> > hm, a compromise.
> >
> > One other concern I have with this is that I expect -mregparm will make
> > kgdb (and now crashdump) less useful. When incoming args are on the stack
> > you have a good chance of being able to see what their value is by walking
> > the stack slots.
> >
> > When the incoming args are in registers I'd expect that it would be a lot
> > harder (or impossible) to work out their value.
> >
> > Have the kdump guys thought about (or encountered) this?
GDB is more than capable of handling this - if your compiler is saving
arguments to the stack and dumping out useful information for the
debugger about where it put them. Recent GCC versions are generally
pretty good about either saving the argument or clearly telling GDB
that it was not saved.
--
Daniel Jacobowitz
CodeSourcery, LLC