source: chapter08/gcc.xml@ f54ecb3

multilib xry111/multilib
Last change on this file since f54ecb3 was d2eb97b, checked in by Thomas Trepl <thomas@…>, 7 weeks ago

Automatic merge of trunk into multilib

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