source: chapter08/gcc.xml@ e131bec

xry111/arm64 xry111/arm64-12.0
Last change on this file since e131bec was e131bec, checked in by Xi Ruoyao <xry111@…>, 12 months ago

Merge remote-tracking branch 'origin/trunk' into xry111/arm64

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