llvm-ar.rst 11 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292
  1. llvm-ar - LLVM archiver
  2. =======================
  3. .. program:: llvm-ar
  4. SYNOPSIS
  5. --------
  6. **llvm-ar** [-]{dmpqrtx}[Rabfikou] [relpos] [count] <archive> [files...]
  7. DESCRIPTION
  8. -----------
  9. The **llvm-ar** command is similar to the common Unix utility, ``ar``. It
  10. archives several files together into a single file. The intent for this is
  11. to produce archive libraries by LLVM bitcode that can be linked into an
  12. LLVM program. However, the archive can contain any kind of file. By default,
  13. **llvm-ar** generates a symbol table that makes linking faster because
  14. only the symbol table needs to be consulted, not each individual file member
  15. of the archive.
  16. The **llvm-ar** command can be used to *read* SVR4, GNU and BSD style archive
  17. files. However, right now it can only write in the GNU format. If an
  18. SVR4 or BSD style archive is used with the ``r`` (replace) or ``q`` (quick
  19. update) operations, the archive will be reconstructed in GNU format.
  20. Here's where **llvm-ar** departs from previous ``ar`` implementations:
  21. *Symbol Table*
  22. Since **llvm-ar** supports bitcode files. The symbol table it creates
  23. is in GNU format and includes both native and bitcode files.
  24. *Long Paths*
  25. Currently **llvm-ar** can read GNU and BSD long file names, but only writes
  26. archives with the GNU format.
  27. OPTIONS
  28. -------
  29. The options to **llvm-ar** are compatible with other ``ar`` implementations.
  30. However, there are a few modifiers (*R*) that are not found in other ``ar``
  31. implementations. The options to **llvm-ar** specify a single basic operation to
  32. perform on the archive, a variety of modifiers for that operation, the name of
  33. the archive file, and an optional list of file names. These options are used to
  34. determine how **llvm-ar** should process the archive file.
  35. The Operations and Modifiers are explained in the sections below. The minimal
  36. set of options is at least one operator and the name of the archive. Typically
  37. archive files end with a ``.a`` suffix, but this is not required. Following
  38. the *archive-name* comes a list of *files* that indicate the specific members
  39. of the archive to operate on. If the *files* option is not specified, it
  40. generally means either "none" or "all" members, depending on the operation.
  41. Operations
  42. ~~~~~~~~~~
  43. d
  44. Delete files from the archive. No modifiers are applicable to this operation.
  45. The *files* options specify which members should be removed from the
  46. archive. It is not an error if a specified file does not appear in the archive.
  47. If no *files* are specified, the archive is not modified.
  48. m[abi]
  49. Move files from one location in the archive to another. The *a*, *b*, and
  50. *i* modifiers apply to this operation. The *files* will all be moved
  51. to the location given by the modifiers. If no modifiers are used, the files
  52. will be moved to the end of the archive. If no *files* are specified, the
  53. archive is not modified.
  54. p
  55. Print files to the standard output. This operation simply prints the
  56. *files* indicated to the standard output. If no *files* are
  57. specified, the entire archive is printed. Printing bitcode files is
  58. ill-advised as they might confuse your terminal settings. The *p*
  59. operation never modifies the archive.
  60. q
  61. Quickly append files to the end of the archive. This operation quickly adds the
  62. *files* to the archive without checking for duplicates that should be
  63. removed first. If no *files* are specified, the archive is not modified.
  64. Because of the way that **llvm-ar** constructs the archive file, its dubious
  65. whether the *q* operation is any faster than the *r* operation.
  66. r[abu]
  67. Replace or insert file members. The *a*, *b*, and *u*
  68. modifiers apply to this operation. This operation will replace existing
  69. *files* or insert them at the end of the archive if they do not exist. If no
  70. *files* are specified, the archive is not modified.
  71. t[v]
  72. Print the table of contents. Without any modifiers, this operation just prints
  73. the names of the members to the standard output. With the *v* modifier,
  74. **llvm-ar** also prints out the file type (B=bitcode, S=symbol
  75. table, blank=regular file), the permission mode, the owner and group, the
  76. size, and the date. If any *files* are specified, the listing is only for
  77. those files. If no *files* are specified, the table of contents for the
  78. whole archive is printed.
  79. x[oP]
  80. Extract archive members back to files. The *o* modifier applies to this
  81. operation. This operation retrieves the indicated *files* from the archive
  82. and writes them back to the operating system's file system. If no
  83. *files* are specified, the entire archive is extract.
  84. Modifiers (operation specific)
  85. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  86. The modifiers below are specific to certain operations. See the Operations
  87. section (above) to determine which modifiers are applicable to which operations.
  88. [a]
  89. When inserting or moving member files, this option specifies the destination of
  90. the new files as being after the *relpos* member. If *relpos* is not found,
  91. the files are placed at the end of the archive.
  92. [b]
  93. When inserting or moving member files, this option specifies the destination of
  94. the new files as being before the *relpos* member. If *relpos* is not
  95. found, the files are placed at the end of the archive. This modifier is
  96. identical to the *i* modifier.
  97. [i]
  98. A synonym for the *b* option.
  99. [o]
  100. When extracting files, this option will cause **llvm-ar** to preserve the
  101. original modification times of the files it writes.
  102. [u]
  103. When replacing existing files in the archive, only replace those files that have
  104. a time stamp than the time stamp of the member in the archive.
  105. Modifiers (generic)
  106. ~~~~~~~~~~~~~~~~~~~
  107. The modifiers below may be applied to any operation.
  108. [c]
  109. For all operations, **llvm-ar** will always create the archive if it doesn't
  110. exist. Normally, **llvm-ar** will print a warning message indicating that the
  111. archive is being created. Using this modifier turns off that warning.
  112. [s]
  113. This modifier requests that an archive index (or symbol table) be added to the
  114. archive. This is the default mode of operation. The symbol table will contain
  115. all the externally visible functions and global variables defined by all the
  116. bitcode files in the archive.
  117. [S]
  118. This modifier is the opposite of the *s* modifier. It instructs **llvm-ar** to
  119. not build the symbol table. If both *s* and *S* are used, the last modifier to
  120. occur in the options will prevail.
  121. [v]
  122. This modifier instructs **llvm-ar** to be verbose about what it is doing. Each
  123. editing operation taken against the archive will produce a line of output saying
  124. what is being done.
  125. STANDARDS
  126. ---------
  127. The **llvm-ar** utility is intended to provide a superset of the IEEE Std 1003.2
  128. (POSIX.2) functionality for ``ar``. **llvm-ar** can read both SVR4 and BSD4.4 (or
  129. macOS) archives. If the ``f`` modifier is given to the ``x`` or ``r`` operations
  130. then **llvm-ar** will write SVR4 compatible archives. Without this modifier,
  131. **llvm-ar** will write BSD4.4 compatible archives that have long names
  132. immediately after the header and indicated using the "#1/ddd" notation for the
  133. name in the header.
  134. FILE FORMAT
  135. -----------
  136. The file format for LLVM Archive files is similar to that of BSD 4.4 or macOS
  137. archive files. In fact, except for the symbol table, the ``ar`` commands on those
  138. operating systems should be able to read LLVM archive files. The details of the
  139. file format follow.
  140. Each archive begins with the archive magic number which is the eight printable
  141. characters "!<arch>\n" where \n represents the newline character (0x0A).
  142. Following the magic number, the file is composed of even length members that
  143. begin with an archive header and end with a \n padding character if necessary
  144. (to make the length even). Each file member is composed of a header (defined
  145. below), an optional newline-terminated "long file name" and the contents of
  146. the file.
  147. The fields of the header are described in the items below. All fields of the
  148. header contain only ASCII characters, are left justified and are right padded
  149. with space characters.
  150. name - char[16]
  151. This field of the header provides the name of the archive member. If the name is
  152. longer than 15 characters or contains a slash (/) character, then this field
  153. contains ``#1/nnn`` where ``nnn`` provides the length of the name and the ``#1/``
  154. is literal. In this case, the actual name of the file is provided in the ``nnn``
  155. bytes immediately following the header. If the name is 15 characters or less, it
  156. is contained directly in this field and terminated with a slash (/) character.
  157. date - char[12]
  158. This field provides the date of modification of the file in the form of a
  159. decimal encoded number that provides the number of seconds since the epoch
  160. (since 00:00:00 Jan 1, 1970) per Posix specifications.
  161. uid - char[6]
  162. This field provides the user id of the file encoded as a decimal ASCII string.
  163. This field might not make much sense on non-Unix systems. On Unix, it is the
  164. same value as the st_uid field of the stat structure returned by the stat(2)
  165. operating system call.
  166. gid - char[6]
  167. This field provides the group id of the file encoded as a decimal ASCII string.
  168. This field might not make much sense on non-Unix systems. On Unix, it is the
  169. same value as the st_gid field of the stat structure returned by the stat(2)
  170. operating system call.
  171. mode - char[8]
  172. This field provides the access mode of the file encoded as an octal ASCII
  173. string. This field might not make much sense on non-Unix systems. On Unix, it
  174. is the same value as the st_mode field of the stat structure returned by the
  175. stat(2) operating system call.
  176. size - char[10]
  177. This field provides the size of the file, in bytes, encoded as a decimal ASCII
  178. string.
  179. fmag - char[2]
  180. This field is the archive file member magic number. Its content is always the
  181. two characters back tick (0x60) and newline (0x0A). This provides some measure
  182. utility in identifying archive files that have been corrupted.
  183. offset - vbr encoded 32-bit integer
  184. The offset item provides the offset into the archive file where the bitcode
  185. member is stored that is associated with the symbol. The offset value is 0
  186. based at the start of the first "normal" file member. To derive the actual
  187. file offset of the member, you must add the number of bytes occupied by the file
  188. signature (8 bytes) and the symbol tables. The value of this item is encoded
  189. using variable bit rate encoding to reduce the size of the symbol table.
  190. Variable bit rate encoding uses the high bit (0x80) of each byte to indicate
  191. if there are more bytes to follow. The remaining 7 bits in each byte carry bits
  192. from the value. The final byte does not have the high bit set.
  193. length - vbr encoded 32-bit integer
  194. The length item provides the length of the symbol that follows. Like this
  195. *offset* item, the length is variable bit rate encoded.
  196. symbol - character array
  197. The symbol item provides the text of the symbol that is associated with the
  198. *offset*. The symbol is not terminated by any character. Its length is provided
  199. by the *length* field. Note that is allowed (but unwise) to use non-printing
  200. characters (even 0x00) in the symbol. This allows for multiple encodings of
  201. symbol names.
  202. EXIT STATUS
  203. -----------
  204. If **llvm-ar** succeeds, it will exit with 0. A usage error, results
  205. in an exit code of 1. A hard (file system typically) error results in an
  206. exit code of 2. Miscellaneous or unknown errors result in an
  207. exit code of 3.
  208. SEE ALSO
  209. --------
  210. ar(1)