source: chapter08/gcc.xml@ c093e6b

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

Automatic merge of trunk into multilib

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