source: chapter08/gcc.xml@ 91f9a17

12.0 12.0-rc1 12.1 12.1-rc1 12.2 12.2-rc1 multilib trunk xry111/arm64 xry111/arm64-12.0 xry111/clfs-ng xry111/loongarch xry111/loongarch-12.0 xry111/loongarch-12.1 xry111/loongarch-12.2 xry111/mips64el xry111/multilib xry111/update-glibc
Last change on this file since 91f9a17 was f40b2e7, checked in by Xi Ruoyao <xry111@…>, 14 months ago

gcc: Document new test failures with Glibc-2.38

Well, the analyzer failures are introduced by literally *my* Glibc
change [1] and I'll sort them out for GCC 14...

And the ASAN failures seem caused by the introduction of
isoc23_strtol (the libsanitizer does not know to intercept it). I'll
test with LLVM once I reach it in BLFS (LLVM is the upstream of
libsanitizer) and make a bug report.

limits-exprparen.c also fails to me, it needs "ulimit -s 65536" instead
of "ulimit -s 32768" in my build but maybe it's caused by my custom
*FLAGS.

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