source: chapter08/gcc.xml@ 651a9ea

xry111/loongarch xry111/loongarch-12.1 xry111/loongarch-12.2
Last change on this file since 651a9ea was 289f284, checked in by Xi Ruoyao <xry111@…>, 8 months ago

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

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