|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:||Christopher Brian Colohan <email@example.com>|
|Date:||22 May 1999 02:56:52 -0400|
|Organization:||Carnegie Mellon Univ. -- Computer Science Dept.|
"S. Bochkarev" <firstname.lastname@example.org> writes:
> 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 ?
I believe the Microsoft Developer's Network includes all the available
documentation on the object formats. Last time I used it it was not
100% accurate, but it was useful.
> 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 ?
This information may be contained in the fixups/relocation entries.
> b) If it is:
> - which C/C++ compiler can generate them ?
> - which linker can work with them ?
I'm not sure.
> c) Which from C-compilers can effectively delete the
> local unused procedures (without conflicts with ANSI-
> definitions of the preprocessor) ?
I know that IBM's VisualAge C++ for Windows and OS/2 did this in the
linker as of about 4 years ago -- but it used the OMF object format
and not MS-COFF as the compiler output.
Return to the
Search the comp.compilers archives again.