Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Re: <em>I do not see much benefit of using it other than reducing file search time for each of object files.</em></p> <p>Your understanding of the benefit is not quite right. Archives reduce the workload of resolving individual <em>symbols</em>.</p> <p>If you link a program out of many individual <code>.o</code> files, the linker has to consider them all at the same time. The references can go in any direction. The very last <code>.o</code> on the command line can call a function in the very first <code>.o</code> and vice versa.</p> <p>This is not the case (by default, at least) with archives. With archives, functions in the earlier archives can only make references to symbols whose definitions appear in the later archives. (This is also related to the the traditional Unix convention why the <code>-l</code> linker options go at the end of the command line!!! Your <code>.o</code> files first, then the command line.)</p> <p>This means that once an archive appears which defines a symbol, you can be sure that the later archives do not use that symbol any more. Which means that you can remove it from your data structures. You are basically "done" linking that particular library; it has satisfied the prior references, and all that remains is to satisfy ITS unresolved references. If you order the linking process right, and the software is nicely layered, you can minimize how many symbols are outstanding at any time.</p> <p>Linux is more than 20 years old now and its build system has a long and rich history, just like the code. Archives were not used originally; I think that started in <code>2.6</code> only. Also, dependencies were once generated by a GNU awk script. People built the kernel on 25 Mhz 386 boxes with 4 megs of RAM, haha.</p> <p>Archives are used today because there was a need for them with the kernel getting larger. It's not just for the heck of it!</p>
    singulars
    1. This table or related slice is empty.
    1. POUse of archive files for compilation: why, and is there any alternative?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USKaz
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POUse of archive files for compilation: why, and is there any alternative?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI said "by default" because there is a way to make the linker take a group of archives and resolve them in any direction: the dash-parenthesis command line arguments. E.g. `ld ... -\( libx.a liby.a libz.a -\)`. The dash-parenthesis arguments enclose selected groups of archives. They are necessary if the archives have circular references. The GNU `ld` man page warns that this may have a significant performance penalty.
      singulars
      1. PO
      1. USKaz
    2. COThank you very much for your detailed answer about the linker internals! The distinction in the treatments of object files and archives looks interesting, and your explanation made me understand some of weird things I experienced with libc compilation (because it too uses a lot of archives in its compilation..)
      singulars
      1. PO
      1. USSangman Kim
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload