source: chapter08/gcc.xml@ d8c2d84

xry111/arm64
Last change on this file since d8c2d84 was d8c2d84, checked in by Xi Ruoyao <xry111@…>, 5 months ago

Merge remote-tracking branch 'origin/trunk' into xry111/arm64

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