[已解决]求论坛中（外）的 GCC/G++ 相关的优秀的教程帖子

奶茶newfish

记得之前在论坛的那个板块下看到过 GCC/G++ 相关的帖子，但是忘记收藏了。
现在想求一篇好的文章。同时也记录一下。

有奖回答，1/2 的概率中奖

最佳答案

月排行榜 / 总排行榜

人造人

2021-9-2 20:46:52

奶茶newfish 发表于 2021-9-2 20:37
是的是的，我看了一下官网，没找到 API

就是编译选项吧？
一般来说，下面这个就够了

1. gcc -g -Wall -o main main.c

复制代码

1.        gcc [-c|-S|-E] [-std=standard]
   
2.            [-g] [-pg] [-Olevel]
   
3.            [-Wwarn...] [-Wpedantic]
   
4.            [-Idir...] [-Ldir...]
   
5.            [-Dmacro[=defn]...] [-Umacro]
   
6.            [-foption...] [-mmachine-option...]
   
7.            [-o outfile] [@file] infile...
   
8. 
   
9.        Only the most useful options are listed here; see below for the
   
10.        remainder.  g++ accepts mostly the same options as gcc.

复制代码

1. 
   
2.        -g  Produce debugging information in the operating system's native
   
3.            format (stabs, COFF, XCOFF, or DWARF).  GDB can work with this
   
4.            debugging information.
   
5. 
   
6.            On most systems that use stabs format, -g enables use of extra
   
7.            debugging information that only GDB can use; this extra information
   
8.            makes debugging work better in GDB but probably makes other
   
9.            debuggers crash or refuse to read the program.  If you want to
   
10.            control for certain whether to generate the extra information, use
    
11.            -gstabs+, -gstabs, -gxcoff+, -gxcoff, or -gvms (see below).

复制代码

1.            -Wall turns on the following warning flags:
   
2. 
   
3.            -Waddress -Warray-bounds=1 (only with -O2) -Warray-parameter=2 (C
   
4.            and Objective-C only) -Wbool-compare -Wbool-operation
   
5.            -Wc++11-compat  -Wc++14-compat -Wcatch-value (C++ and Objective-C++
   
6.            only) -Wchar-subscripts -Wcomment -Wduplicate-decl-specifier (C and
   
7.            Objective-C only) -Wenum-compare (in C/ObjC; this is on by default
   
8.            in C++) -Wformat -Wformat-overflow -Wformat-truncation
   
9.            -Wint-in-bool-context -Wimplicit (C and Objective-C only)
   
10.            -Wimplicit-int (C and Objective-C only)
    
11.            -Wimplicit-function-declaration (C and Objective-C only)
    
12.            -Winit-self (only for C++) -Wlogical-not-parentheses -Wmain (only
    
13.            for C/ObjC and unless -ffreestanding) -Wmaybe-uninitialized
    
14.            -Wmemset-elt-size -Wmemset-transposed-args -Wmisleading-indentation
    
15.            (only for C/C++) -Wmissing-attributes -Wmissing-braces (only for
    
16.            C/ObjC) -Wmultistatement-macros -Wnarrowing (only for C++)
    
17.            -Wnonnull -Wnonnull-compare -Wopenmp-simd -Wparentheses
    
18.            -Wpessimizing-move (only for C++) -Wpointer-sign
    
19.            -Wrange-loop-construct (only for C++) -Wreorder -Wrestrict
    
20.            -Wreturn-type -Wsequence-point -Wsign-compare (only in C++)
    
21.            -Wsizeof-array-div -Wsizeof-pointer-div -Wsizeof-pointer-memaccess
    
22.            -Wstrict-aliasing -Wstrict-overflow=1 -Wswitch
    
23.            -Wtautological-compare -Wtrigraphs -Wuninitialized
    
24.            -Wunknown-pragmas -Wunused-function -Wunused-label -Wunused-value
    
25.            -Wunused-variable -Wvla-parameter (C and Objective-C only)
    
26.            -Wvolatile-register-var -Wzero-length-bounds
    
27. 
    
28.            Note that some warning flags are not implied by -Wall.  Some of
    
29.            them warn about constructions that users generally do not consider
    
30.            questionable, but which occasionally you might wish to check for;
    
31.            others warn about constructions that are necessary or hard to avoid
    
32.            in some cases, and there is no simple way to modify the code to
    
33.            suppress the warning. Some of them are enabled by -Wextra but many
    
34.            of them must be enabled individually.

复制代码

1.        -o file
   
2.            Place the primary output in file file.  This applies to whatever
   
3.            sort of output is being produced, whether it be an executable file,
   
4.            an object file, an assembler file or preprocessed C code.
   
5. 
   
6.            If -o is not specified, the default is to put an executable file in
   
7.            a.out, the object file for source.suffix in source.o, its assembler
   
8.            file in source.s, a precompiled header file in source.suffix.gch,
   
9.            and all preprocessed C source on standard output.
   
10. 
    
11.            Though -o names only the primary output, it also affects the naming
    
12.            of auxiliary and dump outputs.  See the examples below.  Unless
    
13.            overridden, both auxiliary outputs and dump outputs are placed in
    
14.            the same directory as the primary output.  In auxiliary outputs,
    
15.            the suffix of the input file is replaced with that of the auxiliary
    
16.            output file type; in dump outputs, the suffix of the dump file is
    
17.            appended to the input file suffix.  In compilation commands, the
    
18.            base name of both auxiliary and dump outputs is that of the primary
    
19.            output file type; in dump outputs, the suffix of the dump file is
    
20.            appended to the input file suffix.  In compilation commands, the
    
21.            base name of both auxiliary and dump outputs is that of the primary
    
22.            output; in compile and link commands, the primary output name,
    
23.            minus the executable suffix, is combined with the input file name.
    
24.            If both share the same base name, disregarding the suffix, the
    
25.            result of the combination is that base name, otherwise, they are
    
26.            concatenated, separated by a dash.
    
27. 
    
28.                    gcc -c foo.c ...
    
29. 
    
30.            will use foo.o as the primary output, and place aux outputs and
    
31.            dumps next to it, e.g., aux file foo.dwo for -gsplit-dwarf, and
    
32.            dump file foo.c.???r.final for -fdump-rtl-final.
    
33. 
    
34.            If a non-linker output file is explicitly specified, aux and dump
    
35.            files by default take the same base name:
    
36. 
    
37.                    gcc -c foo.c -o dir/foobar.o ...
    
38. 
    
39.            will name aux outputs dir/foobar.* and dump outputs dir/foobar.c.*.
    
40. 
    
41.            A linker output will instead prefix aux and dump outputs:
    
42. 
    
43.                    gcc foo.c bar.c -o dir/foobar ...
    
44. 
    
45.            will generally name aux outputs dir/foobar-foo.* and
    
46.            dir/foobar-bar.*, and dump outputs dir/foobar-foo.c.* and
    
47.            dir/foobar-bar.c.*.
    
48. 
    
49.            The one exception to the above is when the executable shares the
    
50.            base name with the single input:
    
51. 
    
52.                    gcc foo.c -o dir/foo ...
    
53. 
    
54.            in which case aux outputs are named dir/foo.* and dump outputs
    
55.            named dir/foo.c.*.
    
56. 
    
57.            The location and the names of auxiliary and dump outputs can be
    
58.            adjusted by the options -dumpbase, -dumpbase-ext, -dumpdir,
    
59.            -save-temps=cwd, and -save-temps=obj.

复制代码

跳转到最佳答案楼层

人造人

你指的是 GCC/G++ 的使用教程？
man 手册加百度完全够用

人造人

哦，再加 Google 翻译
Google 翻译对程序员比较友好，有道翻译相对来说要差一点
也许说成是差很多？居然翻译出一个完全相反的结果，^_^

奶茶newfish

人造人 发表于 2021-9-2 11:55
你指的是 GCC/G++ 的使用教程？
man 手册加百度完全够用

是的是的，我看了一下官网，没找到 API

人造人

奶茶newfish 发表于 2021-9-2 20:37
是的是的，我看了一下官网，没找到 API

就是编译选项吧？
一般来说，下面这个就够了

1. gcc -g -Wall -o main main.c

复制代码

1.        gcc [-c|-S|-E] [-std=standard]
   
2.            [-g] [-pg] [-Olevel]
   
3.            [-Wwarn...] [-Wpedantic]
   
4.            [-Idir...] [-Ldir...]
   
5.            [-Dmacro[=defn]...] [-Umacro]
   
6.            [-foption...] [-mmachine-option...]
   
7.            [-o outfile] [@file] infile...
   
8. 
   
9.        Only the most useful options are listed here; see below for the
   
10.        remainder.  g++ accepts mostly the same options as gcc.

复制代码

1. 
   
2.        -g  Produce debugging information in the operating system's native
   
3.            format (stabs, COFF, XCOFF, or DWARF).  GDB can work with this
   
4.            debugging information.
   
5. 
   
6.            On most systems that use stabs format, -g enables use of extra
   
7.            debugging information that only GDB can use; this extra information
   
8.            makes debugging work better in GDB but probably makes other
   
9.            debuggers crash or refuse to read the program.  If you want to
   
10.            control for certain whether to generate the extra information, use
    
11.            -gstabs+, -gstabs, -gxcoff+, -gxcoff, or -gvms (see below).

复制代码

1.            -Wall turns on the following warning flags:
   
2. 
   
3.            -Waddress -Warray-bounds=1 (only with -O2) -Warray-parameter=2 (C
   
4.            and Objective-C only) -Wbool-compare -Wbool-operation
   
5.            -Wc++11-compat  -Wc++14-compat -Wcatch-value (C++ and Objective-C++
   
6.            only) -Wchar-subscripts -Wcomment -Wduplicate-decl-specifier (C and
   
7.            Objective-C only) -Wenum-compare (in C/ObjC; this is on by default
   
8.            in C++) -Wformat -Wformat-overflow -Wformat-truncation
   
9.            -Wint-in-bool-context -Wimplicit (C and Objective-C only)
   
10.            -Wimplicit-int (C and Objective-C only)
    
11.            -Wimplicit-function-declaration (C and Objective-C only)
    
12.            -Winit-self (only for C++) -Wlogical-not-parentheses -Wmain (only
    
13.            for C/ObjC and unless -ffreestanding) -Wmaybe-uninitialized
    
14.            -Wmemset-elt-size -Wmemset-transposed-args -Wmisleading-indentation
    
15.            (only for C/C++) -Wmissing-attributes -Wmissing-braces (only for
    
16.            C/ObjC) -Wmultistatement-macros -Wnarrowing (only for C++)
    
17.            -Wnonnull -Wnonnull-compare -Wopenmp-simd -Wparentheses
    
18.            -Wpessimizing-move (only for C++) -Wpointer-sign
    
19.            -Wrange-loop-construct (only for C++) -Wreorder -Wrestrict
    
20.            -Wreturn-type -Wsequence-point -Wsign-compare (only in C++)
    
21.            -Wsizeof-array-div -Wsizeof-pointer-div -Wsizeof-pointer-memaccess
    
22.            -Wstrict-aliasing -Wstrict-overflow=1 -Wswitch
    
23.            -Wtautological-compare -Wtrigraphs -Wuninitialized
    
24.            -Wunknown-pragmas -Wunused-function -Wunused-label -Wunused-value
    
25.            -Wunused-variable -Wvla-parameter (C and Objective-C only)
    
26.            -Wvolatile-register-var -Wzero-length-bounds
    
27. 
    
28.            Note that some warning flags are not implied by -Wall.  Some of
    
29.            them warn about constructions that users generally do not consider
    
30.            questionable, but which occasionally you might wish to check for;
    
31.            others warn about constructions that are necessary or hard to avoid
    
32.            in some cases, and there is no simple way to modify the code to
    
33.            suppress the warning. Some of them are enabled by -Wextra but many
    
34.            of them must be enabled individually.

复制代码

1.        -o file
   
2.            Place the primary output in file file.  This applies to whatever
   
3.            sort of output is being produced, whether it be an executable file,
   
4.            an object file, an assembler file or preprocessed C code.
   
5. 
   
6.            If -o is not specified, the default is to put an executable file in
   
7.            a.out, the object file for source.suffix in source.o, its assembler
   
8.            file in source.s, a precompiled header file in source.suffix.gch,
   
9.            and all preprocessed C source on standard output.
   
10. 
    
11.            Though -o names only the primary output, it also affects the naming
    
12.            of auxiliary and dump outputs.  See the examples below.  Unless
    
13.            overridden, both auxiliary outputs and dump outputs are placed in
    
14.            the same directory as the primary output.  In auxiliary outputs,
    
15.            the suffix of the input file is replaced with that of the auxiliary
    
16.            output file type; in dump outputs, the suffix of the dump file is
    
17.            appended to the input file suffix.  In compilation commands, the
    
18.            base name of both auxiliary and dump outputs is that of the primary
    
19.            output file type; in dump outputs, the suffix of the dump file is
    
20.            appended to the input file suffix.  In compilation commands, the
    
21.            base name of both auxiliary and dump outputs is that of the primary
    
22.            output; in compile and link commands, the primary output name,
    
23.            minus the executable suffix, is combined with the input file name.
    
24.            If both share the same base name, disregarding the suffix, the
    
25.            result of the combination is that base name, otherwise, they are
    
26.            concatenated, separated by a dash.
    
27. 
    
28.                    gcc -c foo.c ...
    
29. 
    
30.            will use foo.o as the primary output, and place aux outputs and
    
31.            dumps next to it, e.g., aux file foo.dwo for -gsplit-dwarf, and
    
32.            dump file foo.c.???r.final for -fdump-rtl-final.
    
33. 
    
34.            If a non-linker output file is explicitly specified, aux and dump
    
35.            files by default take the same base name:
    
36. 
    
37.                    gcc -c foo.c -o dir/foobar.o ...
    
38. 
    
39.            will name aux outputs dir/foobar.* and dump outputs dir/foobar.c.*.
    
40. 
    
41.            A linker output will instead prefix aux and dump outputs:
    
42. 
    
43.                    gcc foo.c bar.c -o dir/foobar ...
    
44. 
    
45.            will generally name aux outputs dir/foobar-foo.* and
    
46.            dir/foobar-bar.*, and dump outputs dir/foobar-foo.c.* and
    
47.            dir/foobar-bar.c.*.
    
48. 
    
49.            The one exception to the above is when the executable shares the
    
50.            base name with the single input:
    
51. 
    
52.                    gcc foo.c -o dir/foo ...
    
53. 
    
54.            in which case aux outputs are named dir/foo.* and dump outputs
    
55.            named dir/foo.c.*.
    
56. 
    
57.            The location and the names of auxiliary and dump outputs can be
    
58.            adjusted by the options -dumpbase, -dumpbase-ext, -dumpdir,
    
59.            -save-temps=cwd, and -save-temps=obj.

复制代码

人造人

奶茶newfish 发表于 2021-9-2 20:37
是的是的，我看了一下官网，没找到 API

1. man gcc

复制代码

web.wdhk

c语言中文
博客园
C语言论坛

奶茶newfish

人造人 发表于 2021-9-2 20:47

好的好的，谢谢啦

不大不小甲鱼

1molHF

1molHF

1molHF

burntlime

学习

私が

blahblahfc

学习

万恶的亚撒西

学习学习

noah-py

Miss执

sunwenwu

yalie