source: chapter08/gcc.xml@ 46b5c6b

12.1 12.1-rc1 multilib trunk xry111/arm64 xry111/clfs-ng xry111/loongarch xry111/loongarch-12.1 xry111/mips64el xry111/update-glibc
Last change on this file since 46b5c6b was 46b5c6b, checked in by Xi Ruoyao <xry111@…>, 4 months ago

gcc: Fix libcc1 description

libcpp is the preprocessor library, but it's a static library which is
only used by GCC itself and not installed.

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