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