source: chapter08/gcc.xml@ 3b3454a

multilib
Last change on this file since 3b3454a was 3a4f80c, checked in by Thomas Trepl <thomas@…>, 11 months ago

Merge branch 'trunk' into multilib

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