source: chapter08/gcc.xml@ 964103c

xry111/clfs-ng
Last change on this file since 964103c was 964103c, checked in by Xi Ruoyao <xry111@…>, 9 months ago

Merge branch 'trunk' into xry111/clfs-ng

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