From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,3941ad115e7b9e14 X-Google-Attributes: gid103376,public From: dewar@merv.cs.nyu.edu (Robert Dewar) Subject: Re: GNAT Linker Options & Memory Maps Date: 1997/06/14 Message-ID: #1/1 X-Deja-AN: 248367130 References: <97061310124788@psavax.pwfl.com> Organization: New York University Newsgroups: comp.lang.ada Date: 1997-06-14T00:00:00+00:00 List-Id: Marin asks << There appears to be no way of controlling the link map using the GNAT linker. (I did not recall seeing anything about an option to even print out the link map.) Is there any way of using the linker to control the addresses at which things fall? (Yes, I know Ada gives you an address clause for fixing things in memory. However, I have often failed to get the desired results using address clauses and there are times when it would be much more handy to use the linker to do this.) Also, I did not see any provisions for outputting a symbol table or for specifying a load image format other than the default host system format. (Motorola S-records, maybe?) >> There is no such thing as "the GNAT linker", GNAT uses one of the standard system linkers that are around, and has the capabilities you want if and only if this linker has these capabilities. It is also quite straightforward to change which linker you are using if necessary. But anyway, GNAT is using standard system capabilities. When it comes to linking, if C can do it, then so can GNAT.