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