source: chapter08/gcc.xml@ 328eb6f

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

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

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