source: chapter08/gcc.xml@ 3a72ffa

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

Adopt upstream changes

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