source: chapter08/gcc.xml@ 530771a

multilib
Last change on this file since 530771a was 530771a, checked in by Thomas Trepl (Moody) <thomas@…>, 20 months ago

Automatic merge of trunk into multilib

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