source: chapter08/gcc.xml@ 0d3452a

xry111/arm64 xry111/arm64-12.0
Last change on this file since 0d3452a was 0d3452a, checked in by Xi Ruoyao <xry111@…>, 20 months ago

arm64: gcc: update sanity check output

It looks like a simple "s/x86_64-pc/aarch64-unknown/".

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