source: chapter08/gcc.xml

trunk
Last change on this file was 5f2ba8c, checked in by Xi Ruoyao <xry111@…>, 2 months ago

gcc: Decorate test failures, remove outdated comments, ...

move comments for upstream PR links to correct location.

BTW data-model-4.c is also in analyzer directory, so we can just say 7
analyzer tests.

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