source: chapter08/gcc.xml@ 3ebe876

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

Merge upstream

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