source: chapter08/gcc.xml@ 031db1b

multilib
Last change on this file since 031db1b was 5975e7e, checked in by Thomas Trepl <thomas@…>, 14 months ago

Automatic merge of trunk into multilib

  • Property mode set to 100644
File size: 26.8 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 potentionally
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 Additionally, two tests named <filename>copy.cc</filename> and
201 <filename>pr56837.c</filename> are known to fail.</para>
202
203 <para>A few unexpected failures cannot always be avoided. The GCC developers
204 are usually aware of these issues, but have not resolved them yet.
205 Unless the test results are vastly different from those at the above URL,
206 it is safe to continue.</para>
207
208 <!--note><para>
209 On some combinations of kernel configuration and AMD processors
210 there may be more than 1100 failures in the gcc.target/i386/mpx
211 tests (which are designed to test the MPX option on recent
212 Intel processors). These can safely be ignored on AMD
213 processors. These tests will also fail on Intel processors if MPX support
214 is not enabled in the kernel even though it is present on the CPU.
215 </para></note-->
216
217 <para>Install the package:</para>
218
219<screen><userinput remap="install">make install</userinput></screen>
220
221 <para>The GCC build directory is owned by <systemitem class="username">
222 tester</systemitem> now, and the ownership of the installed header
223 directory (and its content) is incorrect. Change the ownership to the
224 <systemitem class="username">root</systemitem> user and group:</para>
225
226<screen><userinput remap="install">chown -v -R root:root \
227 /usr/lib/gcc/$(gcc -dumpmachine)/&gcc-version;/include{,-fixed}</userinput></screen>
228
229 <para>Create a symlink required by the <ulink
230 url="https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch03s09.html">FHS</ulink>
231 for "historical" reasons.</para>
232
233<screen><userinput remap="install">ln -svr /usr/bin/cpp /usr/lib</userinput></screen>
234 <!-- already done earlier
235 <para>Many packages use the name <command>cc</command> to call the C
236 compiler. To satisfy those packages, create a symlink:</para>
237
238<screen><userinput remap="install">ln -sv gcc /usr/bin/cc</userinput></screen>
239 -->
240 <para>Add a compatibility symlink to enable building programs with
241 Link Time Optimization (LTO):</para>
242
243<screen><userinput remap="install">ln -sfv ../../libexec/gcc/$(gcc -dumpmachine)/&gcc-version;/liblto_plugin.so \
244 /usr/lib/bfd-plugins/</userinput></screen>
245
246 <para>Now that our final toolchain is in place, it is important to again ensure
247 that compiling and linking will work as expected. We do this by performing
248 some sanity checks:</para>
249
250<screen><userinput>echo 'int main(){}' &gt; dummy.c
251cc dummy.c -v -Wl,--verbose &amp;&gt; dummy.log
252readelf -l a.out | grep ': /lib'</userinput></screen>
253
254 <para>There should be no errors,
255 and the output of the last command will be (allowing for
256 platform-specific differences in the dynamic linker name):</para>
257
258<screen><computeroutput>[Requesting program interpreter: /lib64/ld-linux-x86-64.so.2]</computeroutput></screen>
259
260 <para>Now make sure that we're set up to use the correct start files:</para>
261
262<screen><userinput>grep -E -o '/usr/lib.*/S?crt[1in].*succeeded' dummy.log</userinput></screen>
263
264 <para>The output of the last command should be:</para>
265
266<screen><computeroutput>/usr/lib/gcc/x86_64-pc-linux-gnu/&gcc-version;/../../../../lib/Scrt1.o succeeded
267/usr/lib/gcc/x86_64-pc-linux-gnu/&gcc-version;/../../../../lib/crti.o succeeded
268/usr/lib/gcc/x86_64-pc-linux-gnu/&gcc-version;/../../../../lib/crtn.o succeeded</computeroutput></screen>
269
270 <para>Depending on your machine architecture, the above may differ slightly.
271 The difference will be the name of the directory
272 after <filename class="directory">/usr/lib/gcc</filename>. The important
273 thing to look for here is that <command>gcc</command> has found all three
274 <filename>crt*.o</filename> files under the
275 <filename class="directory">/usr/lib</filename> directory.</para>
276
277 <para>Verify that the compiler is searching for the correct header
278 files:</para>
279
280<screen><userinput>grep -B4 '^ /usr/include' dummy.log</userinput></screen>
281
282 <para>This command should return the following output:</para>
283
284<screen><computeroutput>#include &lt;...&gt; search starts here:
285 /usr/lib/gcc/x86_64-pc-linux-gnu/&gcc-version;/include
286 /usr/local/include
287 /usr/lib/gcc/x86_64-pc-linux-gnu/&gcc-version;/include-fixed
288 /usr/include</computeroutput></screen>
289
290 <para>Again, the directory named after your target triplet may be
291 different than the above, depending on your system architecture.</para>
292
293 <para>Next, verify that the new linker is being used with the correct search paths:</para>
294
295<screen><userinput>grep 'SEARCH.*/usr/lib' dummy.log |sed 's|; |\n|g'</userinput></screen>
296
297 <para>References to paths that have components with '-linux-gnu' should
298 be ignored, but otherwise the output of the last command should be:</para>
299
300<screen><computeroutput>SEARCH_DIR("/usr/x86_64-pc-linux-gnu/lib64")
301SEARCH_DIR("/usr/local/lib64")
302SEARCH_DIR("/lib64")
303SEARCH_DIR("/usr/lib64")
304SEARCH_DIR("/usr/x86_64-pc-linux-gnu/lib")
305SEARCH_DIR("/usr/local/lib")
306SEARCH_DIR("/lib")
307SEARCH_DIR("/usr/lib");</computeroutput></screen>
308
309 <para arch="default">A 32-bit system may use a few other directories. For example, here
310 is the output from an i686 machine:</para>
311
312<!-- not using entities here as the dir names has nothing to do with multilib -->
313<screen arch="default"><computeroutput>SEARCH_DIR("/usr/i686-pc-linux-gnu/lib32")
314SEARCH_DIR("/usr/local/lib32")
315SEARCH_DIR("/lib32")
316SEARCH_DIR("/usr/lib32")
317SEARCH_DIR("/usr/i686-pc-linux-gnu/lib")
318SEARCH_DIR("/usr/local/lib")
319SEARCH_DIR("/lib")
320SEARCH_DIR("/usr/lib");</computeroutput></screen>
321
322 <para>Next make sure that we're using the correct libc:</para>
323
324<screen><userinput>grep "/lib.*/libc.so.6 " dummy.log</userinput></screen>
325
326 <para>The output of the last command should be:</para>
327
328<screen><computeroutput>attempt to open /usr/lib/libc.so.6 succeeded</computeroutput></screen>
329
330 <para>Make sure GCC is using the correct dynamic linker:</para>
331
332<screen><userinput>grep found dummy.log</userinput></screen>
333
334 <para>The output of the last command should be (allowing for
335 platform-specific differences in dynamic linker name):</para>
336
337<screen><computeroutput>found ld-linux-x86-64.so.2 at /usr/lib/ld-linux-x86-64.so.2</computeroutput></screen>
338
339 <para>If the output does not appear as shown above or is not received
340 at all, then something is seriously wrong. Investigate and retrace the
341 steps to find out where the problem is and correct it. <!--The most likely
342 reason is that something went wrong with the specs file adjustment.--> Any
343 issues should be resolved before continuing with the process.</para>
344
345 <para>Once everything is working correctly, clean up the test files:</para>
346
347<screen><userinput>rm -v dummy.c a.out dummy.log</userinput></screen>
348
349 <para>Finally, move a misplaced file:</para>
350
351<screen><userinput remap="install">mkdir -pv /usr/share/gdb/auto-load/usr/lib
352mv -v /usr/lib/*gdb.py /usr/share/gdb/auto-load/usr/lib</userinput></screen>
353
354 </sect2>
355
356 <sect2 id="contents-gcc" role="content">
357 <title>Contents of GCC</title>
358
359 <segmentedlist>
360 <segtitle>Installed programs</segtitle>
361 <segtitle>Installed libraries</segtitle>
362 <segtitle>Installed directories</segtitle>
363
364 <seglistitem>
365 <seg>c++, cc (link to gcc), cpp, g++, gcc,
366 gcc-ar, gcc-nm, gcc-ranlib, gcov, gcov-dump, gcov-tool,
367 and lto-dump</seg>
368
369 <seg>libasan.{a,so}, libatomic.{a,so}, libcc1.so, libgcc.a, libgcc_eh.a,
370 libgcc_s.so, libgcov.a, libgomp.{a,so}, libhwasan.{a,so}, libitm.{a,so},
371 liblsan.{a,so}, liblto_plugin.so,
372 libquadmath.{a,so}, libssp.{a,so}, libssp_nonshared.a,
373 libstdc++.{a,so}, libstdc++exp.a, libstdc++fs.a, libsupc++.a, libtsan.{a,so},
374 and libubsan.{a,so}</seg>
375
376 <seg>/usr/include/c++, /usr/lib/gcc, /usr/libexec/gcc, and
377 /usr/share/gcc-&gcc-version;</seg>
378 </seglistitem>
379 </segmentedlist>
380
381 <variablelist>
382 <bridgehead renderas="sect3">Short Descriptions</bridgehead>
383 <?dbfo list-presentation="list"?>
384 <?dbhtml list-presentation="table"?>
385
386 <varlistentry id="c">
387 <term><command>c++</command></term>
388 <listitem>
389 <para>The C++ compiler</para>
390 <indexterm zone="ch-system-gcc c">
391 <primary sortas="b-c++">c++</primary>
392 </indexterm>
393 </listitem>
394 </varlistentry>
395
396 <varlistentry id="cc">
397 <term><command>cc</command></term>
398 <listitem>
399 <para>The C compiler</para>
400 <indexterm zone="ch-system-gcc cc">
401 <primary sortas="b-cc">cc</primary>
402 </indexterm>
403 </listitem>
404 </varlistentry>
405
406 <varlistentry id="cpp">
407 <term><command>cpp</command></term>
408 <listitem>
409 <para>The C preprocessor; it is used by the compiler to expand the
410 #include, #define, and similar directives in the source files</para>
411 <indexterm zone="ch-system-gcc cpp">
412 <primary sortas="b-cpp">cpp</primary>
413 </indexterm>
414 </listitem>
415 </varlistentry>
416
417 <varlistentry id="g">
418 <term><command>g++</command></term>
419 <listitem>
420 <para>The C++ compiler</para>
421 <indexterm zone="ch-system-gcc g">
422 <primary sortas="b-g++">g++</primary>
423 </indexterm>
424 </listitem>
425 </varlistentry>
426
427 <varlistentry id="gcc">
428 <term><command>gcc</command></term>
429 <listitem>
430 <para>The C compiler</para>
431 <indexterm zone="ch-system-gcc gcc">
432 <primary sortas="b-gcc">gcc</primary>
433 </indexterm>
434 </listitem>
435 </varlistentry>
436
437 <varlistentry id="gcc-ar">
438 <term><command>gcc-ar</command></term>
439 <listitem>
440 <para>A wrapper around <command>ar</command> that adds a
441 plugin to the command line. This program is only used
442 to add "link time optimization" and is not useful with the
443 default build options.</para>
444 <indexterm zone="ch-system-gcc gcc-ar">
445 <primary sortas="b-gcc-ar">gc-ar</primary>
446 </indexterm>
447 </listitem>
448 </varlistentry>
449
450 <varlistentry id="gcc-nm">
451 <term><command>gcc-nm</command></term>
452 <listitem>
453 <para>A wrapper around <command>nm</command> that adds a
454 plugin to the command line. This program is only used
455 to add "link time optimization" and is not useful with the
456 default build options.</para>
457 <indexterm zone="ch-system-gcc gcc-nm">
458 <primary sortas="b-gcc-nm">gc-nm</primary>
459 </indexterm>
460 </listitem>
461 </varlistentry>
462
463 <varlistentry id="gcc-ranlib">
464 <term><command>gcc-ranlib</command></term>
465 <listitem>
466 <para>A wrapper around <command>ranlib</command> that adds a
467 plugin to the command line. This program is only used
468 to add "link time optimization" and is not useful with the
469 default build options.</para>
470 <indexterm zone="ch-system-gcc gcc-ranlib">
471 <primary sortas="b-gcc-ranlib">gc-ranlib</primary>
472 </indexterm>
473 </listitem>
474 </varlistentry>
475
476 <varlistentry id="gcov">
477 <term><command>gcov</command></term>
478 <listitem>
479 <para>A coverage testing tool; it is used to analyze programs to
480 determine where optimizations will have the greatest effect</para>
481 <indexterm zone="ch-system-gcc gcov">
482 <primary sortas="b-gcov">gcov</primary>
483 </indexterm>
484 </listitem>
485 </varlistentry>
486
487 <varlistentry id="gcov-dump">
488 <term><command>gcov-dump</command></term>
489 <listitem>
490 <para>Offline gcda and gcno profile dump tool</para>
491 <indexterm zone="ch-system-gcc gcov-dump">
492 <primary sortas="b-gcov-dump">gcov-dump</primary>
493 </indexterm>
494 </listitem>
495 </varlistentry>
496
497 <varlistentry id="gcov-tool">
498 <term><command>gcov-tool</command></term>
499 <listitem>
500 <para>Offline gcda profile processing tool</para>
501 <indexterm zone="ch-system-gcc gcov-tool">
502 <primary sortas="b-gcov-tool">gcov-tool</primary>
503 </indexterm>
504 </listitem>
505 </varlistentry>
506
507 <varlistentry id="lto-dump">
508 <term><command>lto-dump</command></term>
509 <listitem>
510 <para>Tool for dumping object files produced by GCC with LTO
511 enabled</para>
512 <indexterm zone="ch-system-gcc lto-dump">
513 <primary sortas="b-lto-dump">lto-dump</primary>
514 </indexterm>
515 </listitem>
516 </varlistentry>
517
518 <varlistentry id="libasan">
519 <term><filename class="libraryfile">libasan</filename></term>
520 <listitem>
521 <para>The Address Sanitizer runtime library</para>
522 <indexterm zone="ch-system-gcc libasan">
523 <primary sortas="b-libasan">libasan</primary>
524 </indexterm>
525 </listitem>
526 </varlistentry>
527
528 <varlistentry id="libatomic">
529 <term><filename class="libraryfile">libatomic</filename></term>
530 <listitem>
531 <para>GCC atomic built-in runtime library</para>
532 <indexterm zone="ch-system-gcc libatomic">
533 <primary sortas="b-libatomic">libatomic</primary>
534 </indexterm>
535 </listitem>
536 </varlistentry>
537
538 <varlistentry id="libcc1">
539 <term><filename class="libraryfile">libcc1</filename></term>
540 <listitem>
541 <para>The C preprocessing library</para>
542 <indexterm zone="ch-system-gcc libcc1">
543 <primary sortas="b-libcc1">libcc1</primary>
544 </indexterm>
545 </listitem>
546 </varlistentry>
547
548 <varlistentry id="libgcc">
549 <term><filename class="libraryfile">libgcc</filename></term>
550 <listitem>
551 <para>Contains run-time support for <command>gcc</command></para>
552 <indexterm zone="ch-system-gcc libgcc">
553 <primary sortas="c-libgcc">libgcc</primary>
554 </indexterm>
555 </listitem>
556 </varlistentry>
557
558 <varlistentry id="libgcov">
559 <term><filename class="libraryfile">libgcov</filename></term>
560 <listitem>
561 <para>This library is linked into a program when GCC is instructed
562 to enable profiling</para>
563 <indexterm zone="ch-system-gcc libgcov">
564 <primary sortas="c-libgcov">libgcov</primary>
565 </indexterm>
566 </listitem>
567 </varlistentry>
568
569 <varlistentry id="libgomp">
570 <term><filename class="libraryfile">libgomp</filename></term>
571 <listitem>
572 <para>GNU implementation of the OpenMP API for multi-platform
573 shared-memory parallel programming in C/C++ and Fortran</para>
574 <indexterm zone="ch-system-gcc libgomp">
575 <primary sortas="c-libgomp">libgomp</primary>
576 </indexterm>
577 </listitem>
578 </varlistentry>
579
580 <varlistentry id="libhwasan">
581 <term><filename class="libraryfile">libhwasan</filename></term>
582 <listitem>
583 <para>The Hardware-assisted Address Sanitizer runtime library</para>
584 <indexterm zone="ch-system-gcc libhwasan">
585 <primary sortas="c-libhwasan">libhwasan</primary>
586 </indexterm>
587 </listitem>
588 </varlistentry>
589
590 <varlistentry id="libitm">
591 <term><filename class="libraryfile">libitm</filename></term>
592 <listitem>
593 <para>The GNU transactional memory library</para>
594 <indexterm zone="ch-system-gcc libitm">
595 <primary sortas="c-libitm">libitm</primary>
596 </indexterm>
597 </listitem>
598 </varlistentry>
599
600 <varlistentry id="liblsan">
601 <term><filename class="libraryfile">liblsan</filename></term>
602 <listitem>
603 <para>The Leak Sanitizer runtime library</para>
604 <indexterm zone="ch-system-gcc liblsan">
605 <primary sortas="c-liblsan">liblsan</primary>
606 </indexterm>
607 </listitem>
608 </varlistentry>
609
610 <varlistentry id="liblto_plugin">
611 <term><filename class="libraryfile">liblto_plugin</filename></term>
612 <listitem>
613 <para>GCC's LTO plugin allows Binutils to process object files
614 produced by GCC with LTO enabled</para>
615 <indexterm zone="ch-system-gcc liblto_plugin">
616 <primary sortas="c-liblto_plugin">liblto_plugin</primary>
617 </indexterm>
618 </listitem>
619 </varlistentry>
620
621 <varlistentry id="libquadmath">
622 <term><filename class="libraryfile">libquadmath</filename></term>
623 <listitem>
624 <para>GCC Quad Precision Math Library API</para>
625 <indexterm zone="ch-system-gcc libquadmath">
626 <primary sortas="c-libquadmath">libquadmath</primary>
627 </indexterm>
628 </listitem>
629 </varlistentry>
630
631 <varlistentry id="libssp">
632 <term><filename class="libraryfile">libssp</filename></term>
633 <listitem>
634 <para>Contains routines supporting GCC's stack-smashing protection
635 functionality. Normally it is not used, because Glibc also provides
636 those routines.</para>
637 <indexterm zone="ch-system-gcc libssp">
638 <primary sortas="c-libssp">libssp</primary>
639 </indexterm>
640 </listitem>
641 </varlistentry>
642
643 <varlistentry id="libstdc">
644 <term><filename class="libraryfile">libstdc++</filename></term>
645 <listitem>
646 <para>The standard C++ library</para>
647 <indexterm zone="ch-system-gcc libstdc">
648 <primary sortas="c-libstdc++">libstdc++</primary>
649 </indexterm>
650 </listitem>
651 </varlistentry>
652
653 <varlistentry id="libstdcexp">
654 <term><filename class="libraryfile">libstdc++exp</filename></term>
655 <listitem>
656 <para>Experimental C++ Contracts library</para>
657 <indexterm zone="ch-system-gcc libstdcexp">
658 <primary sortas="c-libstdc++exp">libstdc++exp</primary>
659 </indexterm>
660 </listitem>
661 </varlistentry>
662
663 <varlistentry id="libstdcfs">
664 <term><filename class="libraryfile">libstdc++fs</filename></term>
665 <listitem>
666 <para>ISO/IEC TS 18822:2015 Filesystem library</para>
667 <indexterm zone="ch-system-gcc libstdcfs">
668 <primary sortas="c-libstdc++fs">libstdc++fs</primary>
669 </indexterm>
670 </listitem>
671 </varlistentry>
672
673 <varlistentry id="libsupc">
674 <term><filename class="libraryfile">libsupc++</filename></term>
675 <listitem>
676 <para>Provides supporting routines for the C++ programming
677 language</para>
678 <indexterm zone="ch-system-gcc libsupc">
679 <primary sortas="c-libsupc++">libsupc++</primary>
680 </indexterm>
681 </listitem>
682 </varlistentry>
683
684 <varlistentry id="libtsan">
685 <term><filename class="libraryfile">libtsan</filename></term>
686 <listitem>
687 <para>The Thread Sanitizer runtime library</para>
688 <indexterm zone="ch-system-gcc libtsan">
689 <primary sortas="c-libtsan">libtsan</primary>
690 </indexterm>
691 </listitem>
692 </varlistentry>
693
694 <varlistentry id="libubsan">
695 <term><filename class="libraryfile">libubsan</filename></term>
696 <listitem>
697 <para>The Undefined Behavior Sanitizer runtime library</para>
698 <indexterm zone="ch-system-gcc libubsan">
699 <primary sortas="c-libubsan">libubsan</primary>
700 </indexterm>
701 </listitem>
702 </varlistentry>
703
704 </variablelist>
705
706 </sect2>
707
708</sect1>
Note: See TracBrowser for help on using the repository browser.