|link-optimization in C firstname.lastname@example.org (S. Bochkarev) (1999-05-21)|
|Re: link-optimization in C email@example.com (Christopher Brian Colohan) (1999-05-22)|
|Re: link-optimization in C firstname.lastname@example.org (1999-05-22)|
|Re: link-optimization in C email@example.com (Jan Gray) (1999-05-22)|
|Re: link-optimization in C firstname.lastname@example.org (Bill A.) (1999-05-27)|
|Re: link-optimization in C email@example.com (Jeffrey A Law) (1999-05-27)|
|Re: link-optimization in C firstname.lastname@example.org (Bill Fahle) (1999-06-27)|
|From:||"S. Bochkarev" <email@example.com>|
|Date:||21 May 1999 02:21:40 -0400|
|Organization:||Cityline news server|
|Keywords:||linker, question, C++, comment|
Hello All !
Does somebody know: where it is possible to find the correct
description of linker- operations in the last versions of C ++ from
Microsoft and Inprise ?
Practically, the question can be reformulated so:
a) Is there a format of x86-obj-files, where
local references to a code-segment are
especially presented ?
b) If it is:
- which C/C++ compiler can generate them ?
- which linker can work with them ?
c) Which from C-compilers can effectively delete the
local unused procedures (without conflicts with ANSI-
definitions of the preprocessor) ?
[I've seen linkers that garbage collect unused procedures, but not on
Windows systems. I suppose a compiler could put the code for each routine
into a separate COFF section, then the linker could try to figure out what
references what, but it'd be a mess. There is a provision for deleting
duplicate expanded templates and the like, but that depends on all of the
duplicates having an identical mangled name and deleting all but one
of the identically named sections. -John]
Return to the
Search the comp.compilers archives again.