source: chapter08/gcc.xml@ c49c1fb

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

Automatic merge of trunk into multilib

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