source: chapter08/gcc.xml@ 192dda3

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

Automatic merge of trunk into multilib

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