source: chapter08/gcc.xml@ 0fe3bb0

12.0 12.0-rc1 12.1 12.1-rc1 multilib renodr/libudev-from-systemd trunk xry111/arm64 xry111/arm64-12.0 xry111/clfs-ng xry111/loongarch xry111/loongarch-12.0 xry111/loongarch-12.1 xry111/mips64el xry111/update-glibc
Last change on this file since 0fe3bb0 was 0fe3bb0, checked in by Xi Ruoyao <xry111@…>, 12 months ago

Create man page symlinks for awk, cc, pkg-config, and lex

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