source: chapter08/gcc.xml@ bc33d9d

multilib
Last change on this file since bc33d9d was bc33d9d, checked in by Thomas Trepl <thomas@…>, 6 weeks ago

Merge upstream

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