Talk:ILINK64.EXE, the 64-bit Incremental Linker
The reference to "IMPORT32.LIB" should be "import64.a" for ilink64.
Hello,
Could add a section or a linked page that explains how to handle "Fatal: Out of memory" messages from the linker. Bottom line: the IDE simply relays the Fatal message but the linker emits more information about each heap and how much memory was used. For example:
Turbo Incremental Link64 6.40 Copyright (c) 1997-2012 Embarcadero Technologies,
Inc.
Overrun on linker heap: info
Linker Heaps
------------
info 0x12271000 0x12000000
code 0x0487d000 0x08000000
rodata 0x00159000 0x06000000
data 0x029bb000 0x08000000
bss 0x08000000 0x08000000
dwarf_aranges 0x00010000 0x00200000
dwarf_macinfo 0x00010000 0x00200000
dwarf_pubtypes 0x00275000 0x02000000
dwarf_info 0x04e57000 0x06000000
dwarf_abbrev 0x00040000 0x00200000
dwarf_line 0x0124d000 0x02000000
dwarf_str 0x036e0000 0x06000000
dwarf_loc 0x00070000 0x02000000
dwarf_ranges 0x00275000 0x02000000
Fatal: Out of memory
The -GV<heapname>=size can then be used to allocate bigger heap or heaps. For example, to link the release version of the DLL OWLNext library, I am currently using -GHinfo=0x12000000
Cheers,
Bruneau
Response
Thanks, Bruneau, for your information. I have added it to the ILINK64 page.
KrisHouser (talk) 09:26, 13 December 2012 (PST)