visus
/
toolchain-gcc-arm-embedded
Obserwuj 1
Polub 0
Forkuj 0
Kod Zgłoszenia 0 Oczekujące zmiany 0 Wydania 0 Wiki Aktywność
Nie możesz wybrać więcej, niż 25 tematów Tematy muszą się zaczynać od litery lub cyfry, mogą zawierać myślniki ('-') i mogą mieć do 35 znaków.
2 Commity
1 Gałąź
Gałąź: main
Gałęzie Tagi
${ item.name }
Utwórz gałąź ${ searchTerm }
z 'main'
${ noResults }
toolchain-gcc-arm-embedded/share/doc/gcc-arm-none-eabi/html/ld.html/Input-Section-Wildcards.html

218 lines
10KB
Czysty Bezpośredni odnośnik Wina Historia 

  1. <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">

  2. <html>

  3. <!-- This file documents the GNU linker LD

  4. (GNU Arm Embedded Toolchain 10-2020-q4-major)

  5. version 2.35.1.

  6. 

  7. Copyright (C) 1991-2020 Free Software Foundation, Inc.

  8. 

  9. Permission is granted to copy, distribute and/or modify this document

  10. under the terms of the GNU Free Documentation License, Version 1.3

  11. or any later version published by the Free Software Foundation;

  12. with no Invariant Sections, with no Front-Cover Texts, and with no

  13. Back-Cover Texts.  A copy of the license is included in the

  14. section entitled "GNU Free Documentation License". -->

  15. <!-- Created by GNU Texinfo 6.5, http://www.gnu.org/software/texinfo/ -->

  16. <head>

  17. <meta http-equiv="Content-Type" content="text/html; charset=utf-8">

  18. <title>Input Section Wildcards (LD)</title>

  19. 

  20. <meta name="description" content="Input Section Wildcards (LD)">

  21. <meta name="keywords" content="Input Section Wildcards (LD)">

  22. <meta name="resource-type" content="document">

  23. <meta name="distribution" content="global">

  24. <meta name="Generator" content="makeinfo">

  25. <link href="index.html#Top" rel="start" title="Top">

  26. <link href="LD-Index.html#LD-Index" rel="index" title="LD Index">

  27. <link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">

  28. <link href="Input-Section.html#Input-Section" rel="up" title="Input Section">

  29. <link href="Input-Section-Common.html#Input-Section-Common" rel="next" title="Input Section Common">

  30. <link href="Input-Section-Basics.html#Input-Section-Basics" rel="prev" title="Input Section Basics">

  31. <style type="text/css">

  32. <!--

  33. a.summary-letter {text-decoration: none}

  34. blockquote.indentedblock {margin-right: 0em}

  35. blockquote.smallindentedblock {margin-right: 0em; font-size: smaller}

  36. blockquote.smallquotation {font-size: smaller}

  37. div.display {margin-left: 3.2em}

  38. div.example {margin-left: 3.2em}

  39. div.lisp {margin-left: 3.2em}

  40. div.smalldisplay {margin-left: 3.2em}

  41. div.smallexample {margin-left: 3.2em}

  42. div.smalllisp {margin-left: 3.2em}

  43. kbd {font-style: oblique}

  44. pre.display {font-family: inherit}

  45. pre.format {font-family: inherit}

  46. pre.menu-comment {font-family: serif}

  47. pre.menu-preformatted {font-family: serif}

  48. pre.smalldisplay {font-family: inherit; font-size: smaller}

  49. pre.smallexample {font-size: smaller}

  50. pre.smallformat {font-family: inherit; font-size: smaller}

  51. pre.smalllisp {font-size: smaller}

  52. span.nolinebreak {white-space: nowrap}

  53. span.roman {font-family: initial; font-weight: normal}

  54. span.sansserif {font-family: sans-serif; font-weight: normal}

  55. ul.no-bullet {list-style: none}

  56. -->

  57. </style>

  58. 

  59. 

  60. </head>

  61. 

  62. <body lang="en">

  63. <a name="Input-Section-Wildcards"></a>

  64. <div class="header">

  65. <p>

  66. Next: <a href="Input-Section-Common.html#Input-Section-Common" accesskey="n" rel="next">Input Section Common</a>, Previous: <a href="Input-Section-Basics.html#Input-Section-Basics" accesskey="p" rel="prev">Input Section Basics</a>, Up: <a href="Input-Section.html#Input-Section" accesskey="u" rel="up">Input Section</a> &nbsp; [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="LD-Index.html#LD-Index" title="Index" rel="index">Index</a>]</p>

  67. </div>

  68. <hr>

  69. <a name="Input-Section-Wildcard-Patterns"></a>

  70. <h4 class="subsubsection">3.6.4.2 Input Section Wildcard Patterns</h4>

  71. <a name="index-input-section-wildcards"></a>

  72. <a name="index-wildcard-file-name-patterns"></a>

  73. <a name="index-file-name-wildcard-patterns"></a>

  74. <a name="index-section-name-wildcard-patterns"></a>

  75. <p>In an input section description, either the file name or the section

  76. name or both may be wildcard patterns.

  77. </p>

  78. <p>The file name of &lsquo;<samp>*</samp>&rsquo; seen in many examples is a simple wildcard

  79. pattern for the file name.

  80. </p>

  81. <p>The wildcard patterns are like those used by the Unix shell.

  82. </p>

  83. <dl compact="compact">

  84. <dt>&lsquo;<samp>*</samp>&rsquo;</dt>

  85. <dd><p>matches any number of characters

  86. </p></dd>

  87. <dt>&lsquo;<samp>?</samp>&rsquo;</dt>

  88. <dd><p>matches any single character

  89. </p></dd>

  90. <dt>&lsquo;<samp>[<var>chars</var>]</samp>&rsquo;</dt>

  91. <dd><p>matches a single instance of any of the <var>chars</var>; the &lsquo;<samp>-</samp>&rsquo;

  92. character may be used to specify a range of characters, as in

  93. &lsquo;<samp>[a-z]</samp>&rsquo; to match any lower case letter

  94. </p></dd>

  95. <dt>&lsquo;<samp>\</samp>&rsquo;</dt>

  96. <dd><p>quotes the following character

  97. </p></dd>

  98. </dl>

  99. 

  100. <p>When a file name is matched with a wildcard, the wildcard characters

  101. will not match a &lsquo;<samp>/</samp>&rsquo; character (used to separate directory names on

  102. Unix).  A pattern consisting of a single &lsquo;<samp>*</samp>&rsquo; character is an

  103. exception; it will always match any file name, whether it contains a

  104. &lsquo;<samp>/</samp>&rsquo; or not.  In a section name, the wildcard characters will match

  105. a &lsquo;<samp>/</samp>&rsquo; character.

  106. </p>

  107. <p>File name wildcard patterns only match files which are explicitly

  108. specified on the command line or in an <code>INPUT</code> command.  The linker

  109. does not search directories to expand wildcards.

  110. </p>

  111. <p>If a file name matches more than one wildcard pattern, or if a file name

  112. appears explicitly and is also matched by a wildcard pattern, the linker

  113. will use the first match in the linker script.  For example, this

  114. sequence of input section descriptions is probably in error, because the

  115. <samp>data.o</samp> rule will not be used:

  116. </p><div class="smallexample">

  117. <pre class="smallexample">.data : { *(.data) }

  118. .data1 : { data.o(.data) }

  119. </pre></div>

  120. 

  121. <a name="index-SORT_005fBY_005fNAME"></a>

  122. <p>Normally, the linker will place files and sections matched by wildcards

  123. in the order in which they are seen during the link.  You can change

  124. this by using the <code>SORT_BY_NAME</code> keyword, which appears before a wildcard

  125. pattern in parentheses (e.g., <code>SORT_BY_NAME(.text*)</code>).  When the

  126. <code>SORT_BY_NAME</code> keyword is used, the linker will sort the files or sections

  127. into ascending order by name before placing them in the output file.

  128. </p>

  129. <a name="index-SORT_005fBY_005fALIGNMENT"></a>

  130. <p><code>SORT_BY_ALIGNMENT</code> is similar to <code>SORT_BY_NAME</code>.

  131. <code>SORT_BY_ALIGNMENT</code> will sort sections into descending order of

  132. alignment before placing them in the output file.  Placing larger

  133. alignments before smaller alignments can reduce the amount of padding

  134. needed.

  135. </p>

  136. <a name="index-SORT_005fBY_005fINIT_005fPRIORITY"></a>

  137. <p><code>SORT_BY_INIT_PRIORITY</code> is also similar to <code>SORT_BY_NAME</code>.

  138. <code>SORT_BY_INIT_PRIORITY</code> will sort sections into ascending

  139. numerical order of the GCC init_priority attribute encoded in the

  140. section name before placing them in the output file.  In

  141. <code>.init_array.NNNNN</code> and <code>.fini_array.NNNNN</code>, <code>NNNNN</code> is

  142. the init_priority.  In <code>.ctors.NNNNN</code> and <code>.dtors.NNNNN</code>,

  143. <code>NNNNN</code> is 65535 minus the init_priority.

  144. </p>

  145. <a name="index-SORT"></a>

  146. <p><code>SORT</code> is an alias for <code>SORT_BY_NAME</code>.

  147. </p>

  148. <p>When there are nested section sorting commands in linker script, there

  149. can be at most 1 level of nesting for section sorting commands.

  150. </p>

  151. <ol>

  152. <li> <code>SORT_BY_NAME</code> (<code>SORT_BY_ALIGNMENT</code> (wildcard section pattern)).

  153. It will sort the input sections by name first, then by alignment if two

  154. sections have the same name.

  155. </li><li> <code>SORT_BY_ALIGNMENT</code> (<code>SORT_BY_NAME</code> (wildcard section pattern)).

  156. It will sort the input sections by alignment first, then by name if two

  157. sections have the same alignment.

  158. </li><li> <code>SORT_BY_NAME</code> (<code>SORT_BY_NAME</code> (wildcard section pattern)) is

  159. treated the same as <code>SORT_BY_NAME</code> (wildcard section pattern).

  160. </li><li> <code>SORT_BY_ALIGNMENT</code> (<code>SORT_BY_ALIGNMENT</code> (wildcard section pattern))

  161. is treated the same as <code>SORT_BY_ALIGNMENT</code> (wildcard section pattern).

  162. </li><li> All other nested section sorting commands are invalid.

  163. </li></ol>

  164. 

  165. <p>When both command-line section sorting option and linker script

  166. section sorting command are used, section sorting command always

  167. takes precedence over the command-line option.

  168. </p>

  169. <p>If the section sorting command in linker script isn&rsquo;t nested, the

  170. command-line option will make the section sorting command to be

  171. treated as nested sorting command.

  172. </p>

  173. <ol>

  174. <li> <code>SORT_BY_NAME</code> (wildcard section pattern ) with

  175. <samp>--sort-sections alignment</samp> is equivalent to

  176. <code>SORT_BY_NAME</code> (<code>SORT_BY_ALIGNMENT</code> (wildcard section pattern)).

  177. </li><li> <code>SORT_BY_ALIGNMENT</code> (wildcard section pattern) with

  178. <samp>--sort-section name</samp> is equivalent to

  179. <code>SORT_BY_ALIGNMENT</code> (<code>SORT_BY_NAME</code> (wildcard section pattern)).

  180. </li></ol>

  181. 

  182. <p>If the section sorting command in linker script is nested, the

  183. command-line option will be ignored.

  184. </p>

  185. <a name="index-SORT_005fNONE"></a>

  186. <p><code>SORT_NONE</code> disables section sorting by ignoring the command-line

  187. section sorting option.

  188. </p>

  189. <p>If you ever get confused about where input sections are going, use the

  190. &lsquo;<samp>-M</samp>&rsquo; linker option to generate a map file.  The map file shows

  191. precisely how input sections are mapped to output sections.

  192. </p>

  193. <p>This example shows how wildcard patterns might be used to partition

  194. files.  This linker script directs the linker to place all &lsquo;<samp>.text</samp>&rsquo;

  195. sections in &lsquo;<samp>.text</samp>&rsquo; and all &lsquo;<samp>.bss</samp>&rsquo; sections in &lsquo;<samp>.bss</samp>&rsquo;.

  196. The linker will place the &lsquo;<samp>.data</samp>&rsquo; section from all files beginning

  197. with an upper case character in &lsquo;<samp>.DATA</samp>&rsquo;; for all other files, the

  198. linker will place the &lsquo;<samp>.data</samp>&rsquo; section in &lsquo;<samp>.data</samp>&rsquo;.

  199. </p><div class="smallexample">

  200. <pre class="smallexample">SECTIONS {

  201.   .text : { *(.text) }

  202.   .DATA : { [A-Z]*(.data) }

  203.   .data : { *(.data) }

  204.   .bss : { *(.bss) }

  205. }

  206. </pre></div>

  207. 

  208. <hr>

  209. <div class="header">

  210. <p>

  211. Next: <a href="Input-Section-Common.html#Input-Section-Common" accesskey="n" rel="next">Input Section Common</a>, Previous: <a href="Input-Section-Basics.html#Input-Section-Basics" accesskey="p" rel="prev">Input Section Basics</a>, Up: <a href="Input-Section.html#Input-Section" accesskey="u" rel="up">Input Section</a> &nbsp; [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="LD-Index.html#LD-Index" title="Index" rel="index">Index</a>]</p>

  212. </div>

  213. 

  214. 

  215. 

  216. </body>

  217. </html>