This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
RE: excessive stab information
- From: "Andy Chittenden" <AChittenden at bluearc dot com>
- To: "Daniel Jacobowitz" <drow at false dot org>,"Ian Lance Taylor" <ian at airs dot com>
- Cc: "Dave Korn" <dave dot korn at artimi dot com>,<binutils at sourceware dot org>,"Martin Dorey" <mdorey at bluearc dot com>
- Date: Thu, 28 Apr 2005 16:33:54 +0100
- Subject: RE: excessive stab information
> > ... Second, it seems to me that it will
> > slow down a stabs link slightly, ...
for us, it did speed it up a little!
> > ... Most people do not refer to the same header file using two
> > different names.
This comes about as we "publish" headers that define public interfaces
to subsystems into a "public" directory that other subsystems can
#include from. We do this via symlinks. The "duplicate" stabs come about
by virtue of the publishing directory finding the original header
and the using directory using the published one.
This is not the first environment in which I've seen this technique
used.
>
> I don't think it's a good idea even then. It assumes that
> the paths in
> stabs refer to files on the system where the linker is running.
... but that's a danger with the existing scheme without using realpath.
Given that the symbols within the BINCL would have to match exactly to
get duplicate stab suppression, I don't see that as a problem.
--
Andy, BlueArc Engineering