public inbox for linuxppc-dev@ozlabs.org
 help / color / mirror / Atom feed
From: Anton Blanchard <anton@samba.org>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: linuxppc-dev@ozlabs.org, Michael Neuling <mikey@neuling.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bootgraph: fix for use with dot symbols
Date: Wed, 28 Jan 2009 21:56:01 +1100	[thread overview]
Message-ID: <20090128105601.GB18368@kryten> (raw)
In-Reply-To: <497FE4E7.8070303@linux.intel.com>


Hi Arjan,

> question for the ppc folks.... why does the "print symbol" magic format string
> thing print a dot symbol and not the real function name?
> Should that be fixed instead?

We have two symbols for each function, foo points to the function
descriptor, and .foo points to the instruction text. If we were to strip
the '.' when we print symbols then it would become harder to diagnose
some failures (eg branching to the function descriptor instead of the
instruction text).

Anton

  reply	other threads:[~2009-01-28 10:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-28  3:30 [PATCH] bootgraph: fix for use with dot symbols Michael Neuling
2009-01-28  4:53 ` Arjan van de Ven
2009-01-28 10:56   ` Anton Blanchard [this message]
2009-02-08  0:57     ` Michael Neuling

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=20090128105601.GB18368@kryten \
    --to=anton@samba.org \
    --cc=arjan@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mikey@neuling.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