Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dan@debian.org>
To: Vivek Goyal <vgoyal@in.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>, Adrian Bunk <bunk@stusta.de>,
	fastboot@lists.osdl.org, linux-kernel@vger.kernel.org,
	gdb@sources.redhat.com
Subject: Re: [Fastboot] Re: [-mm patch] i386: enable REGPARM by default
Date: Mon, 27 Jun 2005 14:00:00 -0000	[thread overview]
Message-ID: <20050627140029.GB29121@nevyn.them.org> (raw)
In-Reply-To: <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


  reply	other threads:[~2005-06-27 14:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050624200916.GJ6656@stusta.de>
     [not found] ` <20050624132826.4cdfb63c.akpm@osdl.org>
2005-06-27 13:30   ` Vivek Goyal
2005-06-27 14:00     ` Daniel Jacobowitz [this message]
2005-06-28  4:51       ` Vivek Goyal
2005-06-28 11:24         ` Vivek Goyal
2005-06-28 20:00           ` Mark Kettenis
2005-06-29  8:35             ` Vivek Goyal
2005-06-29 10:08               ` Mark Kettenis
2005-06-29 11:47                 ` Vivek Goyal

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=20050627140029.GB29121@nevyn.them.org \
    --to=dan@debian.org \
    --cc=akpm@osdl.org \
    --cc=bunk@stusta.de \
    --cc=fastboot@lists.osdl.org \
    --cc=gdb@sources.redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vgoyal@in.ibm.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