Changeset 255504f
- Timestamp:
- 09/23/2003 02:27:47 AM (21 years ago)
- Branches:
- 10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v5_0, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- 94cb9c22
- Parents:
- b036adc
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
bookinfo.xml
rb036adc r255504f 22 22 23 23 <legalnotice> 24 <para>Copyright (c) 1999-200 2, Gerard Beekmans</para>24 <para>Copyright (c) 1999-2003, Gerard Beekmans</para> 25 25 26 26 <para>All rights reserved.</para> -
chapter01/changelog.xml
rb036adc r255504f 95 95 </para></listitem> 96 96 97 <listitem><para>September 22nd, 2003 [jeremy]: Removed the make command from 98 DejaGNU, since it performs nothing.</para></listitem> 97 <listitem><para>September 22nd, 2003 [jwrober]: Chapter 5 - Updated the Why 98 Static page to more accurately represent the difference between statically and 99 dynamically linked binaries. Thanks to Ian Molton for point this out. Fixes 100 Bug 602.</para></listitem> 101 102 <listitem><para>September 22nd, 2003 [jeremy]: Removed the make 103 command from DejaGNU, since it performs nothing.</para></listitem> 99 104 100 105 <listitem><para>September 22nd, 2003 [jeremy]: Removed the -k from TCL's make -
chapter05/whystatic.xml
rb036adc r255504f 12 12 <filename>glibc/index.html</filename> somewhere on your host system.</para> 13 13 14 <para>There are two ways of linking the functions from a library to a program 15 that uses them: statically or dynamically. When a program is linked 16 statically, the code of the used functions is included in the executable, 17 resulting in a rather bulky program. When a program is dynamically linked, 18 what is included is a reference to the linker, the name of the library, and 19 the name of the function, resulting in a much smaller executable. This 20 executable has the disadvantage of being somewhat slower than a statically 21 linked one, as the linking at run time takes a few moments.</para> 14 <para>There are two ways of linking the functions from a library to a program 15 that uses them: statically or dynamically. When a program is linked 16 statically, the code of the used functions is included in the executable, 17 resulting in a rather bulky program. When a program is dynamically linked, 18 what is included is a reference to the linker, the name of the library, and 19 the name of the function, resulting in a much smaller executable. Under 20 certain circumstances, this executable can have the disadvantage of being 21 somewhat slower than a statically linked one, as the linking at run time takes 22 a few moments. It should be noted, however, that under normal circumstances on 23 today's hardware, a dynamically linked executable will be faster than a 24 statically linked one as the library function being called by the dynamically 25 linked executable has a good chance of already being loaded in your system's 26 RAM.</para> 22 27 23 28 <para>Aside from this small drawback, dynamic linking has two major advantages
Note:
See TracChangeset
for help on using the changeset viewer.