source: chapter08/gcc.xml@ b3a55dc

multilib xry111/multilib
Last change on this file since b3a55dc was 9bc9f43, checked in by Thomas Trepl <thomas@…>, 7 months ago

Automatic merge of trunk into multilib

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