Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@davemloft.net>
To: schwab@suse.de
Cc: pgilliam@us.ibm.com, gdb-patches@sourceware.org
Subject: Re: Use DWARF CFI frame unwinder on powerpc
Date: Tue, 09 May 2006 18:01:00 -0000	[thread overview]
Message-ID: <20060509.110014.123240405.davem@davemloft.net> (raw)
In-Reply-To: <jeody7hz16.fsf@sykes.suse.de>

From: Andreas Schwab <schwab@suse.de>
Date: Tue, 09 May 2006 19:46:13 +0200

> That is presumably a gcc problem:
> 
> 	/* NOTE: cagney/2003-09-05: CFI should specify the disposition
> 	   of all debug info registers.  If it doesn't, complain (but
> 	   not too loudly).  It turns out that GCC assumes that an
> 	   unspecified register implies "same value" when CFI (draft
> 	   7) specifies nothing at all.  Such a register could equally
> 	   be interpreted as "undefined".  Also note that this check
> 	   isn't sufficient; it only checks that all registers in the
> 	   range [0 .. max column] are specified, and won't detect
> 	   problems when a debug info register falls outside of the
> 	   table.  We need a way of iterating through all the valid
> 	   DWARF2 register numbers.  */
> 
> Andreas.

I really think this warning message should be off by default,
9 times out of 10 when it triggers the situation is completely
harmless.


  reply	other threads:[~2006-05-09 18:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-09 14:16 Andreas Schwab
2006-05-09 17:17 ` PAUL GILLIAM
2006-05-09 17:23   ` Daniel Jacobowitz
2006-05-09 22:26     ` PAUL GILLIAM
2006-05-09 17:46   ` Andreas Schwab
2006-05-09 18:01     ` David S. Miller [this message]
2006-05-09 18:39       ` Daniel Jacobowitz
2006-05-09 21:07         ` David S. Miller
2006-05-15 16:46 ` Daniel Jacobowitz
2006-05-15 19:10   ` Mark Kettenis
2006-05-15 20:43     ` Daniel Jacobowitz

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=20060509.110014.123240405.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=gdb-patches@sourceware.org \
    --cc=pgilliam@us.ibm.com \
    --cc=schwab@suse.de \
    /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