1 | <?xml version="1.0" encoding="UTF-8"?>
|
---|
2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
|
---|
3 | "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
|
---|
4 | <!ENTITY % general-entities SYSTEM "../general.ent">
|
---|
5 | %general-entities;
|
---|
6 | ]>
|
---|
7 |
|
---|
8 | <sect1 id="ch-system-gcc" role="wrap">
|
---|
9 | <?dbhtml filename="gcc.html"?>
|
---|
10 |
|
---|
11 | <sect1info condition="script">
|
---|
12 | <productname>gcc</productname>
|
---|
13 | <productnumber>&gcc-version;</productnumber>
|
---|
14 | <address>&gcc-url;</address>
|
---|
15 | </sect1info>
|
---|
16 |
|
---|
17 | <title>GCC-&gcc-version;</title>
|
---|
18 |
|
---|
19 | <indexterm zone="ch-system-gcc">
|
---|
20 | <primary sortas="a-GCC">GCC</primary>
|
---|
21 | </indexterm>
|
---|
22 |
|
---|
23 | <sect2 role="package">
|
---|
24 | <title/>
|
---|
25 |
|
---|
26 | <para>The GCC package contains the GNU compiler collection, which includes
|
---|
27 | the C and C++ compilers.</para>
|
---|
28 |
|
---|
29 | <segmentedlist>
|
---|
30 | <segtitle>&buildtime;</segtitle>
|
---|
31 | <segtitle>&diskspace;</segtitle>
|
---|
32 |
|
---|
33 | <seglistitem>
|
---|
34 | <seg>&gcc-fin-sbu;</seg>
|
---|
35 | <seg>&gcc-fin-du;</seg>
|
---|
36 | </seglistitem>
|
---|
37 | </segmentedlist>
|
---|
38 |
|
---|
39 | </sect2>
|
---|
40 |
|
---|
41 | <sect2 role="installation">
|
---|
42 | <title>Installation of GCC</title>
|
---|
43 |
|
---|
44 | <para>Set the default directory name for
|
---|
45 | 64-bit libraries to <quote>lib</quote>:</para>
|
---|
46 |
|
---|
47 | <screen><userinput remap="pre">sed -e 's/lib64/lib/' \
|
---|
48 | -i.orig gcc/config/loongarch/{t-linux,linux.h}</userinput></screen>
|
---|
49 |
|
---|
50 | <para>The GCC documentation recommends building GCC in a dedicated build directory:</para>
|
---|
51 |
|
---|
52 | <screen><userinput remap="pre">mkdir -v build
|
---|
53 | cd build</userinput></screen>
|
---|
54 |
|
---|
55 | <para>Prepare GCC for compilation:</para>
|
---|
56 |
|
---|
57 | <screen><userinput remap="configure">../configure --prefix=/usr \
|
---|
58 | LD=ld \
|
---|
59 | --enable-languages=c,c++ \
|
---|
60 | --enable-default-pie \
|
---|
61 | --enable-default-ssp \
|
---|
62 | --enable-host-pie \
|
---|
63 | --disable-multilib \
|
---|
64 | --disable-bootstrap \
|
---|
65 | --disable-fixincludes \
|
---|
66 | --with-system-zlib</userinput></screen>
|
---|
67 |
|
---|
68 | <para>GCC supports seven different computer languages, but the
|
---|
69 | prerequisites for most of them have not yet been installed. See the
|
---|
70 | <ulink url="&blfs-book;general/gcc.html">BLFS Book GCC page</ulink>
|
---|
71 | for instructions on how to build all of GCC's supported languages.</para>
|
---|
72 |
|
---|
73 | <variablelist>
|
---|
74 | <title>The meaning of the new configure parameters:</title>
|
---|
75 |
|
---|
76 | <varlistentry>
|
---|
77 | <term><parameter>LD=ld</parameter></term>
|
---|
78 | <listitem>
|
---|
79 | <para>This parameter makes the configure script use the ld program installed
|
---|
80 | by the Binutils package built earlier in this chapter, rather than
|
---|
81 | the cross-built version which would otherwise be used.</para>
|
---|
82 | </listitem>
|
---|
83 | </varlistentry>
|
---|
84 |
|
---|
85 | <varlistentry>
|
---|
86 | <term><parameter>--disable-fixincludes</parameter></term>
|
---|
87 | <listitem>
|
---|
88 | <para>By default, during the installation of GCC some system
|
---|
89 | headers would be <quote>fixed</quote> to be used with GCC. This
|
---|
90 | is not necessary for a modern Linux system, and potentially
|
---|
91 | harmful if a package is reinstalled after installing GCC. This
|
---|
92 | switch prevents GCC from <quote>fixing</quote> the headers.</para>
|
---|
93 | </listitem>
|
---|
94 | </varlistentry>
|
---|
95 |
|
---|
96 | <varlistentry>
|
---|
97 | <term><parameter>--with-system-zlib</parameter></term>
|
---|
98 | <listitem>
|
---|
99 | <para>This switch tells GCC to link to the system installed copy of
|
---|
100 | the Zlib library, rather than its own internal copy.</para>
|
---|
101 | </listitem>
|
---|
102 | </varlistentry>
|
---|
103 | </variablelist>
|
---|
104 |
|
---|
105 | <note>
|
---|
106 | <anchor id="pie-ssp-info" xreflabel="note on PIE and SSP"/>
|
---|
107 | <para>
|
---|
108 | PIE (position-independent executables) are
|
---|
109 | binary programs that can be loaded anywhere in memory. Without PIE,
|
---|
110 | the security feature named ASLR (Address Space Layout Randomization)
|
---|
111 | can be applied for the shared libraries, but not for the executables
|
---|
112 | themselves. Enabling PIE allows ASLR for the executables in addition to
|
---|
113 | the shared libraries, and mitigates some attacks based on fixed
|
---|
114 | addresses of sensitive code or data in the executables.
|
---|
115 | </para>
|
---|
116 | <para>
|
---|
117 | SSP (Stack Smashing Protection) is a technique to ensure
|
---|
118 | that the parameter stack is not corrupted. Stack corruption can,
|
---|
119 | for example, alter the return address of a subroutine,
|
---|
120 | thus transferring control to some dangerous code
|
---|
121 | (existing in the program or shared libraries, or injected by the
|
---|
122 | attacker somehow).
|
---|
123 | </para>
|
---|
124 | </note>
|
---|
125 |
|
---|
126 | <para>Compile the package:</para>
|
---|
127 |
|
---|
128 | <screen><userinput remap="make">make</userinput></screen>
|
---|
129 |
|
---|
130 | <important>
|
---|
131 | <para>In this section, the test suite for GCC is considered
|
---|
132 | important, but it takes a long time. First-time builders are
|
---|
133 | encouraged to run the test suite. The time to run the tests can be
|
---|
134 | reduced significantly by adding -jx to the <command>make -k check</command>
|
---|
135 | command below, where x is the number of CPU cores on your system.</para>
|
---|
136 | </important>
|
---|
137 |
|
---|
138 | <para>GCC may need more stack space compiling some extremely complex
|
---|
139 | code patterns. As a precaution for the host distros with a tight stack
|
---|
140 | limit, explicitly set the stack size hard limit to infinite.
|
---|
141 | On most host distros (and the final LFS system) the hard limit is
|
---|
142 | infinite by default, but there is no harm done by setting it explicitly.
|
---|
143 | It's not necessary to change the stack size soft limit because GCC will
|
---|
144 | automatically set it to an appropriate value, as long as the value does
|
---|
145 | not exceed the hard limit:</para>
|
---|
146 |
|
---|
147 | <screen><userinput remap="test">ulimit -s -H unlimited</userinput></screen>
|
---|
148 |
|
---|
149 | <para>Now remove/fix several known test failures:</para>
|
---|
150 |
|
---|
151 | <screen><userinput remap="test">sed -e '/cpython/d' -i ../gcc/testsuite/gcc.dg/plugin/plugin.exp</userinput></screen>
|
---|
152 |
|
---|
153 | <para>Test the results as a non-privileged user, but do not stop at errors:</para>
|
---|
154 |
|
---|
155 | <screen><userinput remap="test">chown -R tester .
|
---|
156 | su tester -c "PATH=$PATH make -k check"</userinput></screen>
|
---|
157 |
|
---|
158 | <para>To extract a summary of the test suite results, run:</para>
|
---|
159 |
|
---|
160 | <screen><userinput remap="test">../contrib/test_summary</userinput></screen>
|
---|
161 |
|
---|
162 | <para>To filter out only the summaries, pipe the output through
|
---|
163 | <userinput>grep -A7 Summ</userinput>.</para>
|
---|
164 |
|
---|
165 | <para>Results can be compared with those located at <ulink
|
---|
166 | url="&test-results;"/> and
|
---|
167 | <ulink url="https://gcc.gnu.org/ml/gcc-testresults/"/>.</para>
|
---|
168 | <!--
|
---|
169 | <para>
|
---|
170 | Eight gcc tests (out of over 185,000):
|
---|
171 | <!- - https://gcc.gnu.org/PR106375 - -><filename>pr56837.c</filename>
|
---|
172 | and seven tests in the <filename class='directory'>analyzer</filename>
|
---|
173 | directory are known to fail.
|
---|
174 |
|
---|
175 | <!- - https://gcc.gnu.org/PR109353 - ->
|
---|
176 | One libstdc++ test (out of over 15000), <filename>copy.cc</filename>, is
|
---|
177 | known to fail.
|
---|
178 |
|
---|
179 | For g++, 21 tests (out of approximately 250,000): 14
|
---|
180 | <quote>AddressSanitizer*</quote>
|
---|
181 | tests and 7 <filename>interception-malloc-test-1.C</filename> tests, are
|
---|
182 | known to fail.
|
---|
183 |
|
---|
184 | Additionally, several tests in the
|
---|
185 | <filename class='directory'>vect</filename> directory are known to fail
|
---|
186 | if the hardware does not support AVX.</para>
|
---|
187 | -->
|
---|
188 |
|
---|
189 | <!-- gen-vect-*: Likely https://gcc.gnu.org/PR113418
|
---|
190 | pr108357.c: https://gcc.gnu.org/PR108357#c5
|
---|
191 | update-threading.c: https://gcc.gnu.org/PR110628
|
---|
192 | vect-117.c: https://gcc.gnu.org/PR113685
|
---|
193 | pr64076: Binutils bug (ld crashes), needs a triage -->
|
---|
194 | <para>The tests named
|
---|
195 | <filename>gen-vect-11b.c</filename>,
|
---|
196 | <filename>gen-vect-11c.c</filename>,
|
---|
197 | <filename>gen-vect-26.c</filename>,
|
---|
198 | <filename>gen-vect-28.c</filename>,
|
---|
199 | <filename>pr64076</filename>,
|
---|
200 | <filename>pr108357.c</filename>,
|
---|
201 | <filename>update-threading.c</filename>,
|
---|
202 | and <filename>vect-117.c</filename> are known to fail.</para>
|
---|
203 |
|
---|
204 | <para>A few unexpected failures cannot always be avoided. In some cases
|
---|
205 | test failures depend on the specific hardware of the system.<!--The GCC developers
|
---|
206 | are usually aware of these issues, but have not resolved them yet.-->
|
---|
207 | Unless the test results are vastly different from those at the above URL,
|
---|
208 | it is safe to continue.</para>
|
---|
209 |
|
---|
210 | <para>Install the package:</para>
|
---|
211 |
|
---|
212 | <screen><userinput remap="install">make install</userinput></screen>
|
---|
213 |
|
---|
214 | <para>The GCC build directory is owned by <systemitem class="username">
|
---|
215 | tester</systemitem> now, and the ownership of the installed header
|
---|
216 | directory (and its content) is incorrect. Change the ownership to the
|
---|
217 | <systemitem class="username">root</systemitem> user and group:</para>
|
---|
218 |
|
---|
219 | <screen><userinput remap="install">chown -v -R root:root \
|
---|
220 | /usr/lib/gcc/$(gcc -dumpmachine)/&gcc-version;/include{,-fixed}</userinput></screen>
|
---|
221 |
|
---|
222 | <para>Create a symlink required by the <ulink
|
---|
223 | url="https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch03s09.html">FHS</ulink>
|
---|
224 | for "historical" reasons.</para>
|
---|
225 |
|
---|
226 | <screen><userinput remap="install">ln -svr /usr/bin/cpp /usr/lib</userinput></screen>
|
---|
227 |
|
---|
228 | <para>Many packages use the name <command>cc</command> to call the C
|
---|
229 | compiler. We've already created <command>cc</command> as a symlink in
|
---|
230 | <xref linkend='ch-tools-gcc-pass2'/>, create its man page as a symlink
|
---|
231 | as well:</para>
|
---|
232 |
|
---|
233 | <screen><userinput remap="install">ln -sv gcc.1 /usr/share/man/man1/cc.1</userinput></screen>
|
---|
234 |
|
---|
235 | <para>Add a compatibility symlink to enable building programs with
|
---|
236 | Link Time Optimization (LTO):</para>
|
---|
237 |
|
---|
238 | <screen><userinput remap="install">ln -sfv ../../libexec/gcc/$(gcc -dumpmachine)/&gcc-version;/liblto_plugin.so \
|
---|
239 | /usr/lib/bfd-plugins/</userinput></screen>
|
---|
240 |
|
---|
241 | <para>Now that our final toolchain is in place, it is important to again ensure
|
---|
242 | that compiling and linking will work as expected. We do this by performing
|
---|
243 | some sanity checks:</para>
|
---|
244 |
|
---|
245 | <screen><userinput>echo 'int main(){}' > dummy.c
|
---|
246 | cc dummy.c -v -Wl,--verbose &> dummy.log
|
---|
247 | readelf -l a.out | grep ': /lib'</userinput></screen>
|
---|
248 |
|
---|
249 | <para>There should be no errors,
|
---|
250 | and the output of the last command will be (allowing for
|
---|
251 | platform-specific differences in the dynamic linker name):</para>
|
---|
252 |
|
---|
253 | <screen><computeroutput>[Requesting program interpreter: /lib64/ld-linux-loongarch-lp64d.so.1]</computeroutput></screen>
|
---|
254 |
|
---|
255 | <para>Now make sure that we're set up to use the correct start files:</para>
|
---|
256 |
|
---|
257 | <screen><userinput>grep -E -o '/usr/lib.*/S?crt[1in].*succeeded' dummy.log</userinput></screen>
|
---|
258 |
|
---|
259 | <para>The output of the last command should be:</para>
|
---|
260 |
|
---|
261 | <screen><computeroutput>/usr/lib/gcc/loongarch64-unknown-linux-gnu/&gcc-version;/../../../../lib/Scrt1.o succeeded
|
---|
262 | /usr/lib/gcc/loongarch64-unknown-linux-gnu/&gcc-version;/../../../../lib/crti.o succeeded
|
---|
263 | /usr/lib/gcc/loongarch64-unknown-linux-gnu/&gcc-version;/../../../../lib/crtn.o succeeded</computeroutput></screen>
|
---|
264 |
|
---|
265 | <para>Depending on your machine architecture, the above may differ slightly.
|
---|
266 | The difference will be the name of the directory
|
---|
267 | after <filename class="directory">/usr/lib/gcc</filename>. The important
|
---|
268 | thing to look for here is that <command>gcc</command> has found all three
|
---|
269 | <filename>crt*.o</filename> files under the
|
---|
270 | <filename class="directory">/usr/lib</filename> directory.</para>
|
---|
271 |
|
---|
272 | <para>Verify that the compiler is searching for the correct header
|
---|
273 | files:</para>
|
---|
274 |
|
---|
275 | <screen><userinput>grep -B4 '^ /usr/include' dummy.log</userinput></screen>
|
---|
276 |
|
---|
277 | <para>This command should return the following output:</para>
|
---|
278 |
|
---|
279 | <screen><computeroutput>#include <...> search starts here:
|
---|
280 | /usr/lib/gcc/loongarch64-unknown-linux-gnu/&gcc-version;/include
|
---|
281 | /usr/local/include
|
---|
282 | /usr/lib/gcc/loongarch64-unknown-linux-gnu/&gcc-version;/include-fixed
|
---|
283 | /usr/include</computeroutput></screen>
|
---|
284 |
|
---|
285 | <para>Again, the directory named after your target triplet may be
|
---|
286 | different than the above, depending on your system architecture.</para>
|
---|
287 |
|
---|
288 | <para>Next, verify that the new linker is being used with the correct search paths:</para>
|
---|
289 |
|
---|
290 | <screen><userinput>grep 'SEARCH.*/usr/lib' dummy.log |sed 's|; |\n|g'</userinput></screen>
|
---|
291 |
|
---|
292 | <para>References to paths that have components with '-linux-gnu' should
|
---|
293 | be ignored, but otherwise the output of the last command should be:</para>
|
---|
294 |
|
---|
295 | <screen><computeroutput>SEARCH_DIR("/usr/loongarch64-unknown-linux-gnu/lib64")
|
---|
296 | SEARCH_DIR("/usr/local/lib64")
|
---|
297 | SEARCH_DIR("/lib64")
|
---|
298 | SEARCH_DIR("/usr/lib64")
|
---|
299 | SEARCH_DIR("/usr/loongarch64-unknown-linux-gnu/lib")
|
---|
300 | SEARCH_DIR("/usr/local/lib")
|
---|
301 | SEARCH_DIR("/lib")
|
---|
302 | SEARCH_DIR("/usr/lib");</computeroutput></screen>
|
---|
303 | <!--
|
---|
304 | <para>A 32-bit system may use a few other directories. For example, here
|
---|
305 | is the output from an i686 machine:</para>
|
---|
306 |
|
---|
307 | <screen><computeroutput>SEARCH_DIR("/usr/i686-pc-linux-gnu/lib32")
|
---|
308 | SEARCH_DIR("/usr/local/lib32")
|
---|
309 | SEARCH_DIR("/lib32")
|
---|
310 | SEARCH_DIR("/usr/lib32")
|
---|
311 | SEARCH_DIR("/usr/i686-pc-linux-gnu/lib")
|
---|
312 | SEARCH_DIR("/usr/local/lib")
|
---|
313 | SEARCH_DIR("/lib")
|
---|
314 | SEARCH_DIR("/usr/lib");</computeroutput></screen>
|
---|
315 | -->
|
---|
316 | <para>Next make sure that we're using the correct libc:</para>
|
---|
317 |
|
---|
318 | <screen><userinput>grep "/lib.*/libc.so.6 " dummy.log</userinput></screen>
|
---|
319 |
|
---|
320 | <para>The output of the last command should be:</para>
|
---|
321 |
|
---|
322 | <screen><computeroutput>attempt to open /usr/lib/libc.so.6 succeeded</computeroutput></screen>
|
---|
323 |
|
---|
324 | <para>Make sure GCC is using the correct dynamic linker:</para>
|
---|
325 |
|
---|
326 | <screen><userinput>grep found dummy.log</userinput></screen>
|
---|
327 |
|
---|
328 | <para>The output of the last command should be (allowing for
|
---|
329 | platform-specific differences in dynamic linker name):</para>
|
---|
330 |
|
---|
331 | <screen><computeroutput>found ld-linux-loongarch-lp64d.so.1 at /usr/lib/ld-linux-loongarch-lp64d.so.1</computeroutput></screen>
|
---|
332 |
|
---|
333 | <para>If the output does not appear as shown above or is not received
|
---|
334 | at all, then something is seriously wrong. Investigate and retrace the
|
---|
335 | steps to find out where the problem is and correct it. <!--The most likely
|
---|
336 | reason is that something went wrong with the specs file adjustment.--> Any
|
---|
337 | issues should be resolved before continuing with the process.</para>
|
---|
338 |
|
---|
339 | <para>Once everything is working correctly, clean up the test files:</para>
|
---|
340 |
|
---|
341 | <screen><userinput>rm -v dummy.c a.out dummy.log</userinput></screen>
|
---|
342 |
|
---|
343 | <para>Finally, move a misplaced file:</para>
|
---|
344 |
|
---|
345 | <screen><userinput remap="install">mkdir -pv /usr/share/gdb/auto-load/usr/lib
|
---|
346 | mv -v /usr/lib/*gdb.py /usr/share/gdb/auto-load/usr/lib</userinput></screen>
|
---|
347 |
|
---|
348 | </sect2>
|
---|
349 |
|
---|
350 | <sect2 id="contents-gcc" role="content">
|
---|
351 | <title>Contents of GCC</title>
|
---|
352 |
|
---|
353 | <segmentedlist>
|
---|
354 | <segtitle>Installed programs</segtitle>
|
---|
355 | <segtitle>Installed libraries</segtitle>
|
---|
356 | <segtitle>Installed directories</segtitle>
|
---|
357 |
|
---|
358 | <seglistitem>
|
---|
359 | <seg>c++, cc (link to gcc), cpp, g++, gcc,
|
---|
360 | gcc-ar, gcc-nm, gcc-ranlib, gcov, gcov-dump, gcov-tool,
|
---|
361 | and lto-dump</seg>
|
---|
362 |
|
---|
363 | <seg>libasan.{a,so}, libatomic.{a,so}, libcc1.so, libgcc.a, libgcc_eh.a,
|
---|
364 | libgcc_s.so, libgcov.a, libgomp.{a,so}, libhwasan.{a,so}, libitm.{a,so},
|
---|
365 | liblsan.{a,so}, liblto_plugin.so,
|
---|
366 | libquadmath.{a,so}, libssp.{a,so}, libssp_nonshared.a,
|
---|
367 | libstdc++.{a,so}, libstdc++exp.a, libstdc++fs.a, libsupc++.a, libtsan.{a,so},
|
---|
368 | and libubsan.{a,so}</seg>
|
---|
369 |
|
---|
370 | <seg>/usr/include/c++, /usr/lib/gcc, /usr/libexec/gcc, and
|
---|
371 | /usr/share/gcc-&gcc-version;</seg>
|
---|
372 | </seglistitem>
|
---|
373 | </segmentedlist>
|
---|
374 |
|
---|
375 | <variablelist>
|
---|
376 | <bridgehead renderas="sect3">Short Descriptions</bridgehead>
|
---|
377 | <?dbfo list-presentation="list"?>
|
---|
378 | <?dbhtml list-presentation="table"?>
|
---|
379 |
|
---|
380 | <varlistentry id="c">
|
---|
381 | <term><command>c++</command></term>
|
---|
382 | <listitem>
|
---|
383 | <para>The C++ compiler</para>
|
---|
384 | <indexterm zone="ch-system-gcc c">
|
---|
385 | <primary sortas="b-c++">c++</primary>
|
---|
386 | </indexterm>
|
---|
387 | </listitem>
|
---|
388 | </varlistentry>
|
---|
389 |
|
---|
390 | <varlistentry id="cc">
|
---|
391 | <term><command>cc</command></term>
|
---|
392 | <listitem>
|
---|
393 | <para>The C compiler</para>
|
---|
394 | <indexterm zone="ch-system-gcc cc">
|
---|
395 | <primary sortas="b-cc">cc</primary>
|
---|
396 | </indexterm>
|
---|
397 | </listitem>
|
---|
398 | </varlistentry>
|
---|
399 |
|
---|
400 | <varlistentry id="cpp">
|
---|
401 | <term><command>cpp</command></term>
|
---|
402 | <listitem>
|
---|
403 | <para>The C preprocessor; it is used by the compiler to expand the
|
---|
404 | #include, #define, and similar directives in the source files</para>
|
---|
405 | <indexterm zone="ch-system-gcc cpp">
|
---|
406 | <primary sortas="b-cpp">cpp</primary>
|
---|
407 | </indexterm>
|
---|
408 | </listitem>
|
---|
409 | </varlistentry>
|
---|
410 |
|
---|
411 | <varlistentry id="g">
|
---|
412 | <term><command>g++</command></term>
|
---|
413 | <listitem>
|
---|
414 | <para>The C++ compiler</para>
|
---|
415 | <indexterm zone="ch-system-gcc g">
|
---|
416 | <primary sortas="b-g++">g++</primary>
|
---|
417 | </indexterm>
|
---|
418 | </listitem>
|
---|
419 | </varlistentry>
|
---|
420 |
|
---|
421 | <varlistentry id="gcc">
|
---|
422 | <term><command>gcc</command></term>
|
---|
423 | <listitem>
|
---|
424 | <para>The C compiler</para>
|
---|
425 | <indexterm zone="ch-system-gcc gcc">
|
---|
426 | <primary sortas="b-gcc">gcc</primary>
|
---|
427 | </indexterm>
|
---|
428 | </listitem>
|
---|
429 | </varlistentry>
|
---|
430 |
|
---|
431 | <varlistentry id="gcc-ar">
|
---|
432 | <term><command>gcc-ar</command></term>
|
---|
433 | <listitem>
|
---|
434 | <para>A wrapper around <command>ar</command> that adds a
|
---|
435 | plugin to the command line. This program is only used
|
---|
436 | to add "link time optimization" and is not useful with the
|
---|
437 | default build options.</para>
|
---|
438 | <indexterm zone="ch-system-gcc gcc-ar">
|
---|
439 | <primary sortas="b-gcc-ar">gc-ar</primary>
|
---|
440 | </indexterm>
|
---|
441 | </listitem>
|
---|
442 | </varlistentry>
|
---|
443 |
|
---|
444 | <varlistentry id="gcc-nm">
|
---|
445 | <term><command>gcc-nm</command></term>
|
---|
446 | <listitem>
|
---|
447 | <para>A wrapper around <command>nm</command> that adds a
|
---|
448 | plugin to the command line. This program is only used
|
---|
449 | to add "link time optimization" and is not useful with the
|
---|
450 | default build options.</para>
|
---|
451 | <indexterm zone="ch-system-gcc gcc-nm">
|
---|
452 | <primary sortas="b-gcc-nm">gc-nm</primary>
|
---|
453 | </indexterm>
|
---|
454 | </listitem>
|
---|
455 | </varlistentry>
|
---|
456 |
|
---|
457 | <varlistentry id="gcc-ranlib">
|
---|
458 | <term><command>gcc-ranlib</command></term>
|
---|
459 | <listitem>
|
---|
460 | <para>A wrapper around <command>ranlib</command> that adds a
|
---|
461 | plugin to the command line. This program is only used
|
---|
462 | to add "link time optimization" and is not useful with the
|
---|
463 | default build options.</para>
|
---|
464 | <indexterm zone="ch-system-gcc gcc-ranlib">
|
---|
465 | <primary sortas="b-gcc-ranlib">gc-ranlib</primary>
|
---|
466 | </indexterm>
|
---|
467 | </listitem>
|
---|
468 | </varlistentry>
|
---|
469 |
|
---|
470 | <varlistentry id="gcov">
|
---|
471 | <term><command>gcov</command></term>
|
---|
472 | <listitem>
|
---|
473 | <para>A coverage testing tool; it is used to analyze programs to
|
---|
474 | determine where optimizations will have the greatest effect</para>
|
---|
475 | <indexterm zone="ch-system-gcc gcov">
|
---|
476 | <primary sortas="b-gcov">gcov</primary>
|
---|
477 | </indexterm>
|
---|
478 | </listitem>
|
---|
479 | </varlistentry>
|
---|
480 |
|
---|
481 | <varlistentry id="gcov-dump">
|
---|
482 | <term><command>gcov-dump</command></term>
|
---|
483 | <listitem>
|
---|
484 | <para>Offline gcda and gcno profile dump tool</para>
|
---|
485 | <indexterm zone="ch-system-gcc gcov-dump">
|
---|
486 | <primary sortas="b-gcov-dump">gcov-dump</primary>
|
---|
487 | </indexterm>
|
---|
488 | </listitem>
|
---|
489 | </varlistentry>
|
---|
490 |
|
---|
491 | <varlistentry id="gcov-tool">
|
---|
492 | <term><command>gcov-tool</command></term>
|
---|
493 | <listitem>
|
---|
494 | <para>Offline gcda profile processing tool</para>
|
---|
495 | <indexterm zone="ch-system-gcc gcov-tool">
|
---|
496 | <primary sortas="b-gcov-tool">gcov-tool</primary>
|
---|
497 | </indexterm>
|
---|
498 | </listitem>
|
---|
499 | </varlistentry>
|
---|
500 |
|
---|
501 | <varlistentry id="lto-dump">
|
---|
502 | <term><command>lto-dump</command></term>
|
---|
503 | <listitem>
|
---|
504 | <para>Tool for dumping object files produced by GCC with LTO
|
---|
505 | enabled</para>
|
---|
506 | <indexterm zone="ch-system-gcc lto-dump">
|
---|
507 | <primary sortas="b-lto-dump">lto-dump</primary>
|
---|
508 | </indexterm>
|
---|
509 | </listitem>
|
---|
510 | </varlistentry>
|
---|
511 |
|
---|
512 | <varlistentry id="libasan">
|
---|
513 | <term><filename class="libraryfile">libasan</filename></term>
|
---|
514 | <listitem>
|
---|
515 | <para>The Address Sanitizer runtime library</para>
|
---|
516 | <indexterm zone="ch-system-gcc libasan">
|
---|
517 | <primary sortas="b-libasan">libasan</primary>
|
---|
518 | </indexterm>
|
---|
519 | </listitem>
|
---|
520 | </varlistentry>
|
---|
521 |
|
---|
522 | <varlistentry id="libatomic">
|
---|
523 | <term><filename class="libraryfile">libatomic</filename></term>
|
---|
524 | <listitem>
|
---|
525 | <para>GCC atomic built-in runtime library</para>
|
---|
526 | <indexterm zone="ch-system-gcc libatomic">
|
---|
527 | <primary sortas="b-libatomic">libatomic</primary>
|
---|
528 | </indexterm>
|
---|
529 | </listitem>
|
---|
530 | </varlistentry>
|
---|
531 |
|
---|
532 | <varlistentry id="libcc1">
|
---|
533 | <term><filename class="libraryfile">libcc1</filename></term>
|
---|
534 | <listitem>
|
---|
535 | <para>A library that allows GDB to make use of GCC</para>
|
---|
536 | <indexterm zone="ch-system-gcc libcc1">
|
---|
537 | <primary sortas="b-libcc1">libcc1</primary>
|
---|
538 | </indexterm>
|
---|
539 | </listitem>
|
---|
540 | </varlistentry>
|
---|
541 |
|
---|
542 | <varlistentry id="libgcc">
|
---|
543 | <term><filename class="libraryfile">libgcc</filename></term>
|
---|
544 | <listitem>
|
---|
545 | <para>Contains run-time support for <command>gcc</command></para>
|
---|
546 | <indexterm zone="ch-system-gcc libgcc">
|
---|
547 | <primary sortas="c-libgcc">libgcc</primary>
|
---|
548 | </indexterm>
|
---|
549 | </listitem>
|
---|
550 | </varlistentry>
|
---|
551 |
|
---|
552 | <varlistentry id="libgcov">
|
---|
553 | <term><filename class="libraryfile">libgcov</filename></term>
|
---|
554 | <listitem>
|
---|
555 | <para>This library is linked into a program when GCC is instructed
|
---|
556 | to enable profiling</para>
|
---|
557 | <indexterm zone="ch-system-gcc libgcov">
|
---|
558 | <primary sortas="c-libgcov">libgcov</primary>
|
---|
559 | </indexterm>
|
---|
560 | </listitem>
|
---|
561 | </varlistentry>
|
---|
562 |
|
---|
563 | <varlistentry id="libgomp">
|
---|
564 | <term><filename class="libraryfile">libgomp</filename></term>
|
---|
565 | <listitem>
|
---|
566 | <para>GNU implementation of the OpenMP API for multi-platform
|
---|
567 | shared-memory parallel programming in C/C++ and Fortran</para>
|
---|
568 | <indexterm zone="ch-system-gcc libgomp">
|
---|
569 | <primary sortas="c-libgomp">libgomp</primary>
|
---|
570 | </indexterm>
|
---|
571 | </listitem>
|
---|
572 | </varlistentry>
|
---|
573 |
|
---|
574 | <varlistentry id="libhwasan">
|
---|
575 | <term><filename class="libraryfile">libhwasan</filename></term>
|
---|
576 | <listitem>
|
---|
577 | <para>The Hardware-assisted Address Sanitizer runtime library</para>
|
---|
578 | <indexterm zone="ch-system-gcc libhwasan">
|
---|
579 | <primary sortas="c-libhwasan">libhwasan</primary>
|
---|
580 | </indexterm>
|
---|
581 | </listitem>
|
---|
582 | </varlistentry>
|
---|
583 |
|
---|
584 | <varlistentry id="libitm">
|
---|
585 | <term><filename class="libraryfile">libitm</filename></term>
|
---|
586 | <listitem>
|
---|
587 | <para>The GNU transactional memory library</para>
|
---|
588 | <indexterm zone="ch-system-gcc libitm">
|
---|
589 | <primary sortas="c-libitm">libitm</primary>
|
---|
590 | </indexterm>
|
---|
591 | </listitem>
|
---|
592 | </varlistentry>
|
---|
593 |
|
---|
594 | <varlistentry id="liblsan">
|
---|
595 | <term><filename class="libraryfile">liblsan</filename></term>
|
---|
596 | <listitem>
|
---|
597 | <para>The Leak Sanitizer runtime library</para>
|
---|
598 | <indexterm zone="ch-system-gcc liblsan">
|
---|
599 | <primary sortas="c-liblsan">liblsan</primary>
|
---|
600 | </indexterm>
|
---|
601 | </listitem>
|
---|
602 | </varlistentry>
|
---|
603 |
|
---|
604 | <varlistentry id="liblto_plugin">
|
---|
605 | <term><filename class="libraryfile">liblto_plugin</filename></term>
|
---|
606 | <listitem>
|
---|
607 | <para>GCC's LTO plugin allows Binutils to process object files
|
---|
608 | produced by GCC with LTO enabled</para>
|
---|
609 | <indexterm zone="ch-system-gcc liblto_plugin">
|
---|
610 | <primary sortas="c-liblto_plugin">liblto_plugin</primary>
|
---|
611 | </indexterm>
|
---|
612 | </listitem>
|
---|
613 | </varlistentry>
|
---|
614 |
|
---|
615 | <varlistentry id="libquadmath">
|
---|
616 | <term><filename class="libraryfile">libquadmath</filename></term>
|
---|
617 | <listitem>
|
---|
618 | <para>GCC Quad Precision Math Library API</para>
|
---|
619 | <indexterm zone="ch-system-gcc libquadmath">
|
---|
620 | <primary sortas="c-libquadmath">libquadmath</primary>
|
---|
621 | </indexterm>
|
---|
622 | </listitem>
|
---|
623 | </varlistentry>
|
---|
624 |
|
---|
625 | <varlistentry id="libssp">
|
---|
626 | <term><filename class="libraryfile">libssp</filename></term>
|
---|
627 | <listitem>
|
---|
628 | <para>Contains routines supporting GCC's stack-smashing protection
|
---|
629 | functionality. Normally it is not used, because Glibc also provides
|
---|
630 | those routines.</para>
|
---|
631 | <indexterm zone="ch-system-gcc libssp">
|
---|
632 | <primary sortas="c-libssp">libssp</primary>
|
---|
633 | </indexterm>
|
---|
634 | </listitem>
|
---|
635 | </varlistentry>
|
---|
636 |
|
---|
637 | <varlistentry id="libstdc">
|
---|
638 | <term><filename class="libraryfile">libstdc++</filename></term>
|
---|
639 | <listitem>
|
---|
640 | <para>The standard C++ library</para>
|
---|
641 | <indexterm zone="ch-system-gcc libstdc">
|
---|
642 | <primary sortas="c-libstdc++">libstdc++</primary>
|
---|
643 | </indexterm>
|
---|
644 | </listitem>
|
---|
645 | </varlistentry>
|
---|
646 |
|
---|
647 | <varlistentry id="libstdcexp">
|
---|
648 | <term><filename class="libraryfile">libstdc++exp</filename></term>
|
---|
649 | <listitem>
|
---|
650 | <para>Experimental C++ Contracts library</para>
|
---|
651 | <indexterm zone="ch-system-gcc libstdcexp">
|
---|
652 | <primary sortas="c-libstdc++exp">libstdc++exp</primary>
|
---|
653 | </indexterm>
|
---|
654 | </listitem>
|
---|
655 | </varlistentry>
|
---|
656 |
|
---|
657 | <varlistentry id="libstdcfs">
|
---|
658 | <term><filename class="libraryfile">libstdc++fs</filename></term>
|
---|
659 | <listitem>
|
---|
660 | <para>ISO/IEC TS 18822:2015 Filesystem library</para>
|
---|
661 | <indexterm zone="ch-system-gcc libstdcfs">
|
---|
662 | <primary sortas="c-libstdc++fs">libstdc++fs</primary>
|
---|
663 | </indexterm>
|
---|
664 | </listitem>
|
---|
665 | </varlistentry>
|
---|
666 |
|
---|
667 | <varlistentry id="libsupc">
|
---|
668 | <term><filename class="libraryfile">libsupc++</filename></term>
|
---|
669 | <listitem>
|
---|
670 | <para>Provides supporting routines for the C++ programming
|
---|
671 | language</para>
|
---|
672 | <indexterm zone="ch-system-gcc libsupc">
|
---|
673 | <primary sortas="c-libsupc++">libsupc++</primary>
|
---|
674 | </indexterm>
|
---|
675 | </listitem>
|
---|
676 | </varlistentry>
|
---|
677 |
|
---|
678 | <varlistentry id="libtsan">
|
---|
679 | <term><filename class="libraryfile">libtsan</filename></term>
|
---|
680 | <listitem>
|
---|
681 | <para>The Thread Sanitizer runtime library</para>
|
---|
682 | <indexterm zone="ch-system-gcc libtsan">
|
---|
683 | <primary sortas="c-libtsan">libtsan</primary>
|
---|
684 | </indexterm>
|
---|
685 | </listitem>
|
---|
686 | </varlistentry>
|
---|
687 |
|
---|
688 | <varlistentry id="libubsan">
|
---|
689 | <term><filename class="libraryfile">libubsan</filename></term>
|
---|
690 | <listitem>
|
---|
691 | <para>The Undefined Behavior Sanitizer runtime library</para>
|
---|
692 | <indexterm zone="ch-system-gcc libubsan">
|
---|
693 | <primary sortas="c-libubsan">libubsan</primary>
|
---|
694 | </indexterm>
|
---|
695 | </listitem>
|
---|
696 | </varlistentry>
|
---|
697 |
|
---|
698 | </variablelist>
|
---|
699 |
|
---|
700 | </sect2>
|
---|
701 |
|
---|
702 | </sect1>
|
---|