source: chapter08/gcc.xml@ f0ebf5c

xry111/clfs-ng
Last change on this file since f0ebf5c was 4e28354, checked in by Xi Ruoyao <xry111@…>, 16 months ago

Merge remote-tracking branch 'origin/trunk' into xry111/clfs-ng

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