All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: "H. Peter Anvin" <hpa@linux.intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	linux-arch@vger.kernel.org, Sam Ravnborg <sam@ravnborg.org>
Subject: Re: "N" symbols and System.map
Date: Sat, 02 May 2009 01:10:18 +0200	[thread overview]
Message-ID: <m2preso1wl.fsf@igel.home> (raw)
In-Reply-To: <49FB7692.2000508@linux.intel.com> (H. Peter Anvin's message of "Fri, 01 May 2009 15:24:18 -0700")

"H. Peter Anvin" <hpa@linux.intel.com> writes:

> right now, we filter out symbols that nm tag N, meaning "debugging
> symbols", from System.map.  However, at least on x86, the linker-generated
> symbol _end is tagged N, and in fact is the only N in the entire image.
>
> Are there other architectures which would suffer if N were included in
> System.map, or would that be a reasonable thing to do?

There should not be any N symbols unless you are using stabs debugging.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

  parent reply	other threads:[~2009-05-01 23:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-01 22:24 "N" symbols and System.map H. Peter Anvin
2009-05-01 22:39 ` Luck, Tony
2009-05-01 22:39   ` Luck, Tony
2009-05-01 23:10 ` Andreas Schwab [this message]
2009-05-01 23:21   ` Sam Ravnborg
2009-05-02  0:00     ` H. Peter Anvin
2009-05-04 19:33       ` Sam Ravnborg
2009-05-04 19:33         ` Sam Ravnborg
2009-05-04 19:33         ` Sam Ravnborg
2009-05-04 21:19         ` Andreas Schwab
2009-05-04 21:26           ` H. Peter Anvin
2009-05-04 21:39           ` Luck, Tony
2009-06-05 22:26 ` Sam Ravnborg
2009-06-05 22:28   ` H. Peter Anvin
2009-06-05 22:37     ` Sam Ravnborg
2009-06-05 22:49       ` H. Peter Anvin

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=m2preso1wl.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=hpa@linux.intel.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.