source: chapter08/gcc.xml@ e8e771a

multilib
Last change on this file since e8e771a was e233b611, checked in by Thomas Trepl <thomas@…>, 12 months ago

Automatic merge of trunk into multilib

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