source: chapter08/gcc.xml@ 942172e

multilib xry111/multilib
Last change on this file since 942172e was 44b216e, checked in by Thomas Trepl <thomas@…>, 7 months ago

Automatic merge of trunk into multilib

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