Date: Sat, 6 Jun 2009 00:37:28 +0200
From: Sam Ravnborg <sam@ravnborg.org>
To: "H. Peter Anvin" <hpa@linux.intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-arch@vger.kernel.org
Subject: Re: "N" symbols and System.map
Message-ID: <20090605223728.GP29008@uranus.ravnborg.org>
References: <49FB7692.2000508@linux.intel.com> <20090605222650.GM29008@uranus.ravnborg.org> <4A299C00.1010307@linux.intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4A299C00.1010307@linux.intel.com>
User-Agent: Mutt/1.4.2.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1150
Lines: 31

On Fri, Jun 05, 2009 at 03:28:16PM -0700, H. Peter Anvin wrote:
> Sam Ravnborg wrote:
> > On Fri, May 01, 2009 at 03:24:18PM -0700, H. Peter Anvin wrote:
> >> Hi all,
> >>
> >> 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?
> > 
> > Peter - what is status here?
> > 
> > Do you see _end tagged N with -tip?
> > We landed a lot of changes to vmlinux.lds there.
> > 
> > Needless to say I have not included N symbols for now.
> > 
> 
> I haven't checked it for a bit, as my immediate need for it disappeared,
> but I don't think it's changed.
We can revisit this if needed.

	Sam
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/