CLANG(1)

📦
version 20.1.8 · 4 versions
, in fedora 43, fedora 44

🎀 NAME 🎀

okay so bestie, welcome to CLANG(1) ✨

clang — the Clang C, C++, and Objective-C compiler. that's the whole name section, it's giving short and iconic 💅

🌸 SYNOPSIS 🌸

clang [options] filename ...

literally that's it. options, then filenames. slay. 🫶

💖 DESCRIPTION 💖

so clang is a C, C++, and Objective-C compiler, and it does everything — preprocessing, parsing, optimization, code generation, assembly, and linking, all of it, one tool, no cap. 🔥

depending on which high-level mode setting you pass, Clang will stop before doing a full link. and yes bestie, Clang is super highly integrated, but you still gotta understand the stages of compilation to understand how to invoke it. the stages are:

  • Driver — the clang executable is actually just a small driver that controls the overall execution of other tools like the compiler, assembler and linker. typically you don't need to interact with the driver directly, you just transparently use it to run the other tools. it's giving stage manager energy 👑
  • Preprocessing — this stage handles tokenization of the input source file, macro expansion, #include expansion, and handling of other preprocessor directives. the output is typically called a .i file (for C), a .ii file (for C++), a .mi file (for Objective-C), or a .mii file (for Objective-C++).
  • Parsing and Semantic Analysis — this stage parses the input file, translating preprocessor tokens into a parse tree. once it's in the form of a parse tree, it applies semantic analysis to compute types for expressions as well as determine whether the code is well formed. this stage is responsible for generating most of the compiler warnings as well as parse errors 😭 the output of this stage is an "Abstract Syntax Tree" (AST).
  • Code Generation and Optimization — this stage translates an AST into low-level intermediate code (known as "LLVM IR") and ultimately to machine code. this phase is responsible for optimizing the generated code and handling target-specific code generation. the output is typically called a .s file or "assembly" file.

Clang also supports the use of an integrated assembler, in which the code generator produces object files directly. this avoids the overhead of generating the .s file and of calling the target assembler. efficiency queen ✨

  • Assembler — this stage runs the target assembler to translate the output of the compiler into a target object file. the output is typically called a .o file or "object" file.
  • Linker — this stage runs the target linker to merge multiple object files into an executable or dynamic library. the output is typically called an a.out, .dylib or .so file.

🧚 Clang Static Analyzer 🧚

the Clang Static Analyzer is a tool that scans source code to try to find bugs through code analysis. this tool uses many parts of Clang and is built into the same driver. please see <https://clang-analyzer.llvm.org> for more details on how to use the static analyzer. go look, it's a whole vibe 🦋

✨ OPTIONS ✨

💅 Stage Selection Options

  • -E — run the preprocessor stage.
  • -fsyntax-only — run the preprocessor, parser and semantic analysis stages.
  • -S — run the previous stages as well as LLVM generation and optimization stages and target-specific code generation, producing an assembly file.
  • -c — run all of the above, plus the assembler, generating a target .o object file.
  • no stage selection option — if no stage selection option is specified, all stages above are run, and the linker is run to combine the results into an executable or shared library. the whole pipeline, start to finish, main character energy 🌈

🌸 Language Selection and Mode Options 🌸

  • -x <language> — treat subsequent input files as having type language.
  • -std=<standard> — specify the language standard to compile for. okay bestie, here comes the list, hydrate first 💧

supported values for the C language are:

  • c89, c90, iso9899:1990 — ISO C 1990
  • iso9899:199409 — ISO C 1990 with amendment 1
  • gnu89, gnu90 — ISO C 1990 with GNU extensions
  • c99, iso9899:1999 — ISO C 1999
  • gnu99 — ISO C 1999 with GNU extensions
  • c11, iso9899:2011 — ISO C 2011
  • gnu11 — ISO C 2011 with GNU extensions
  • c17, iso9899:2017 — ISO C 2017
  • gnu17 — ISO C 2017 with GNU extensions

the default C language standard is gnu17, except on PS4, where it is gnu99. not me knowing the PS4 exception, iykyk 😌

supported values for the C++ language are:

  • c++98, c++03 — ISO C++ 1998 with amendments
  • gnu++98, gnu++03 — ISO C++ 1998 with amendments and GNU extensions
  • c++11 — ISO C++ 2011 with amendments
  • gnu++11 — ISO C++ 2011 with amendments and GNU extensions
  • c++14 — ISO C++ 2014 with amendments
  • gnu++14 — ISO C++ 2014 with amendments and GNU extensions
  • c++17 — ISO C++ 2017 with amendments
  • gnu++17 — ISO C++ 2017 with amendments and GNU extensions
  • c++20 — ISO C++ 2020 with amendments
  • gnu++20 — ISO C++ 2020 with amendments and GNU extensions
  • c++23 — ISO C++ 2023 with amendments
  • gnu++23 — ISO C++ 2023 with amendments and GNU extensions
  • c++2c — working draft for C++2c
  • gnu++2c — working draft for C++2c with GNU extensions

the default C++ language standard is gnu++17.

supported values for the OpenCL language are:

  • cl1.0 — OpenCL 1.0
  • cl1.1 — OpenCL 1.1
  • cl1.2 — OpenCL 1.2
  • cl2.0 — OpenCL 2.0

the default OpenCL language standard is cl1.0.

supported values for the CUDA language are:

  • cuda — NVIDIA CUDA(tm)
  • -stdlib=<library> — specify the C++ standard library to use; supported options are libstdc++ and libc++. if not specified, platform default will be used.
  • -rtlib=<library> — specify the compiler runtime library to use; supported options are libgcc and compiler-rt. if not specified, platform default will be used.
  • -ansi — same as -std=c89.
  • -ObjC, -ObjC++ — treat source input files as Objective-C and Object-C++ inputs respectively.
  • -trigraphs — enable trigraphs.
  • -ffreestanding — indicate that the file should be compiled for a freestanding, not a hosted, environment. note that it is assumed that a freestanding environment will additionally provide memcpy, memmove, memset and memcmp implementations, as these are needed for efficient codegen for many programs. so like, you're on your own for the setup but these four are presumed present, k? 🫶
  • -fno-builtin — disable special handling and optimizations of well-known library functions, like strlen() and malloc().
  • -fno-builtin-<function> — disable special handling and optimizations for the specific library function. for example, -fno-builtin-strlen removes any special handling for the strlen() library function.
  • -fno-builtin-std-<function> — disable special handling and optimizations for the specific C++ standard library function in namespace std. for example, -fno-builtin-std-move_if_noexcept removes any special handling for the std::move_if_noexcept() library function.

for C standard library functions that the C++ standard library also provides in namespace std, use -fno-builtin-<function> instead. (important little distinction bestie, don't mix them up 💀)

  • -fmath-errno — indicate that math functions should be treated as updating errno.
  • -fpascal-strings — enable support for Pascal-style strings with "\pfoo".
  • -fms-extensions — enable support for Microsoft extensions.
  • -fmsc-version= — set _MSC_VER. when on Windows, this defaults to either the same value as the currently installed version of cl.exe, or 1933. not set otherwise.
  • -fborland-extensions — enable support for Borland extensions.
  • -fwritable-strings — make all string literals default to writable. this disables uniquing of strings and other optimizations.
  • -flax-vector-conversions, -flax-vector-conversions=<kind>, -fno-lax-vector-conversions — allow loose type checking rules for implicit vector conversions. possible values of <kind>:
    • none: allow no implicit conversions between vectors
    • integer: allow implicit bitcasts between integer vectors of the same overall bit-width
    • all: allow implicit bitcasts between any vectors of the same overall bit-width

<kind> defaults to integer if unspecified.

  • -fblocks — enable the "Blocks" language feature.
  • -fobjc-abi-version=version — select the Objective-C ABI version to use. available versions are 1 (legacy "fragile" ABI), 2 (non-fragile ABI 1), and 3 (non-fragile ABI 2).
  • -fobjc-nonfragile-abi-version=<version> — select the Objective-C non-fragile ABI version to use by default. this will only be used as the Objective-C ABI when the non-fragile ABI is enabled (either via -fobjc-nonfragile-abi, or because it is the platform default).
  • -fobjc-nonfragile-abi, -fno-objc-nonfragile-abi — enable use of the Objective-C non-fragile ABI. on platforms for which this is the default ABI, it can be disabled with -fno-objc-nonfragile-abi.

⭐ Target Selection Options ⭐

Clang fully supports cross compilation as an inherent part of its design. depending on how your version of Clang is configured, it may have support for a number of cross compilers, or may only support a native target. either way, it's built different 💜

  • -arch <architecture> — specify the architecture to build for (Mac OS X specific).
  • -target <architecture> — specify the architecture to build for (all platforms).
  • -mmacos-version-min=<version> — when building for macOS, specify the minimum version supported by your application.
  • -miphoneos-version-min — when building for iPhone OS, specify the minimum version supported by your application.
  • --print-supported-cpus — bestie, this one prints out a whole list of supported processors for the given target (you specify that target with --target=<architecture> or -arch <architecture>). if you don't specify a target at all, the system default target gets used. easy. 🫶
  • -mcpu=?, -mtune=? — acts as an alias for --print-supported-cpus. that's it. that's the tweet.
  • -mcpu=help, -mtune=help — also acts as an alias for --print-supported-cpus. same energy, fr fr.
  • -march=<cpu> — tells Clang to generate code for a specific processor family member and later. for example, if you specify -march=i486, the compiler is allowed to generate instructions that are valid on i486 and later processors, but which may not exist on earlier ones. so don't go running that on some ancient box unless you want a lil 💀 moment.
  • --print-enabled-extensions — prints the list of extensions that are enabled for the target specified by the combination of --target, -march, and -mcpu values. rn, this option is only supported on AArch64 and RISC-V. on RISC-V, this option also prints out the ISA string of enabled extensions. cute. 🌸
  • --print-supported-extensions — prints the list of all extensions that are supported for every CPU target for an architecture (specified through --target=<architecture> or -arch <architecture>). if no target is specified, the system default target will be used. rn, this option is only supported on AArch64 and RISC-V. 🦋

✨ Code Generation Options ✨

  • -O0, -O1, -O2, -O3, -Ofast, -Os, -Oz, -Og, -O, -O4 — specify which optimization level to use, bestie:
    • -O0 means "no optimization": this level compiles the fastest and generates the most debuggable code.
    • -O1 somewhere between -O0 and -O2.
    • -O2 moderate level of optimization which enables most optimizations.
    • -O3 like -O2, except that it enables optimizations that take longer to perform or that may generate larger code (in an attempt to make the program run faster).
    • -Ofast enables all the optimizations from -O3 along with other aggressive optimizations that may violate strict compliance with language standards. this is deprecated in Clang 19 and a warning is emitted that -O3 in combination with -ffast-math should be used instead if the request for non-standard math behavior is intended. there is no timeline yet for removal; the aim is to discourage use of -Ofast due to the surprising behavior of an optimization flag changing the observable behavior of correct code. so like... it's giving "chaos" and the maintainers are politely asking you to stop. 😭
    • -Os like -O2 with extra optimizations to reduce code size.
    • -Oz like -Os (and thus -O2), but reduces code size further.
    • -Og like -O1. in future versions, this option might disable different optimizations in order to improve debuggability.
    • -O equivalent to -O1.
    • -O4 and higher — currently equivalent to -O3.
  • -g, -gline-tables-only, -gmodules — control debug information output. ngl Clang debug information works best at -O0. when more than one option starting with -g is specified, the last one wins:
    • -g generate debug information.
    • -gline-tables-only generate only line table debug information. this allows for symbolicated backtraces with inlining information, but does not include any information about variables, their locations or types.
    • -gmodules generate debug information that contains external references to types defined in Clang modules or precompiled headers instead of emitting redundant debug type information into every object file. this option transparently switches the Clang module format to object file containers that hold the Clang module together with the debug information. when compiling a program that uses Clang modules or precompiled headers, this option produces complete debug information with faster compile times and much smaller object files.
    • > 🚨 heads up: this option should not be used when building static libraries for distribution to other machines because the debug info will contain references to the module cache on the machine the object files in the library were built on. like, it will not travel well.
  • -fstandalone-debug -fno-standalone-debug — Clang supports a number of optimizations to reduce the size of debug information in the binary. they work based on the assumption that the debug type information can be spread out over multiple compilation units. for instance, Clang will not emit type definitions for types that are not needed by a module and could be replaced with a forward declaration. further, Clang will only emit type info for a dynamic C++ class in the module that contains the vtable for the class.
    • the -fstandalone-debug option turns off these optimizations. this is useful when working with 3rd-party libraries that don't come with debug information. this is the default on Darwin. note that Clang will never emit type information for types that are not referenced at all by the program.
  • -feliminate-unused-debug-types — by default, Clang does not emit type information for types that are defined but not used in a program. to retain the debug info for these unused types, the negation -fno-eliminate-unused-debug-types can be used. 🎀
  • -fexceptions — allow exceptions to be thrown through Clang compiled stack frames (on many targets, this will enable unwind information for functions that might have an exception thrown through them). for most targets, this is enabled by default for C++.
  • -ftrapv — generate code to catch integer overflow errors. signed integer overflow is undefined in C. with this flag, extra code is generated to detect this and abort when it happens. so it just 🛑 the second things go sideways.
  • -fvisibility — this flag sets the default visibility level.
  • -fcommon, -fno-common — this flag specifies that variables without initializers get common linkage. it can be disabled with -fno-common.
  • -ftls-model=<model> — set the default thread-local storage (TLS) model to use for thread-local variables. valid values are: "global-dynamic", "local-dynamic", "initial-exec" and "local-exec". the default is "global-dynamic". the default model can be overridden with the tls_model attribute. the compiler will try to choose a more efficient model if possible. 👑
  • -flto, -flto=full, -flto=thin, -emit-llvm — generate output files in LLVM formats, suitable for link time optimization. when used with -S this generates LLVM intermediate language assembly files, otherwise this generates LLVM bitcode format object files (which may be passed to the linker depending on the stage selection options).
    • the default for -flto is "full", in which the LLVM bitcode is suitable for monolithic Link Time Optimization (LTO), where the linker merges all such modules into a single combined module for optimization. with "thin", ThinLTO compilation is invoked instead.
    • > NOTE: on Darwin, when using -flto along with -g and compiling and linking in separate steps, you also need to pass -Wl,-object_path_lto,<lto-filename>.o at the linking step to instruct the ld64 linker not to delete the temporary object file generated during Link Time Optimization (this flag is automatically passed to the linker by Clang if compilation and linking are done in a single step). this allows debugging the executable as well as generating the .dSYM bundle using dsymutil(1). 🔥

🚗 Driver Options 🚗

  • -### — print (but do not run) the commands to run for this compilation.
  • --help — display available options.
  • -Qunused-arguments — do not emit any warnings for unused driver arguments.
  • -Wa,<args> — pass the comma separated arguments in args to the assembler.
  • -Wl,<args> — pass the comma separated arguments in args to the linker.
  • -Wp,<args> — pass the comma separated arguments in args to the preprocessor.
  • -Xanalyzer <arg> — pass arg to the static analyzer.
  • -Xassembler <arg> — pass arg to the assembler.
  • -Xlinker <arg> — pass arg to the linker.
  • -Xpreprocessor <arg> — pass arg to the preprocessor.
  • -o <file> — write output to file.
  • -print-file-name=<file> — print the full library path of file.
  • -print-libgcc-file-name — print the library path for the currently used compiler runtime library ("libgcc.a" or "libclang_rt.builtins.*.a").
  • -print-prog-name=<name> — print the full program path of name.
  • -print-search-dirs — print the paths used for finding libraries and programs.
  • -save-temps — save intermediate compilation results.
  • -save-stats, -save-stats=cwd, -save-stats=obj — save internal code generation (LLVM) statistics to a file in the current directory (-save-stats/-save-stats=cwd) or the directory of the output file (-save-state=obj).
    • you can also use environment variables to control the statistics reporting. setting CC_PRINT_INTERNAL_STAT to 1 enables the feature, the report goes to stdout in JSON format.
    • setting CC_PRINT_INTERNAL_STAT_FILE to a file path makes it report statistics to the given file in the JSON format.
    • note that -save-stats take precedence over CC_PRINT_INTERNAL_STAT and CC_PRINT_INTERNAL_STAT_FILE.
  • -integrated-as, -no-integrated-as — used to enable and disable, respectively, the use of the integrated assembler. whether the integrated assembler is on by default is target dependent.
  • -time — time individual commands.
  • -ftime-report — print timing summary of each stage of compilation.
  • -v — show commands to run and use verbose output.

🔍 Diagnostics Options 🔍

  • -fshow-column, -fshow-source-location, -fcaret-diagnostics, -fdiagnostics-fixit-info, -fdiagnostics-parseable-fixits, -fdiagnostics-print-source-range-info, -fprint-source-range-info, -fdiagnostics-show-option, -fmessage-length — these options control how Clang prints out information about diagnostics (errors and warnings). please see the Clang User's Manual for more information. 📖

✨ Preprocessor Options ✨

okay bestie this is where you get to mess with the preprocessor before it even looks at your file, it's giving time-travel honestly 💫

  • -D<macroname>=<value> — drops an implicit #define into the predefines buffer, which gets read before your source file is preprocessed. sneaky but iconic.
  • -U<macroname> — same energy but backwards: adds an implicit #undef into the predefines buffer, read before the source file is preprocessed. undefining things before they even exist? that's the power 💅
  • -include <filename> — adds an implicit #include into the predefines buffer, read before the source file is preprocessed. like a little surprise header that shows up first.
  • -I<directory> — adds the directory you name to the search path for include files. this is the classic one, you'll use it constantly fr fr.
  • -F<directory> — adds the specified directory to the search path for framework include files. (macOS girlies know 🍎)
  • -nostdinc — do NOT search the standard system directories or the compiler builtin directories for include files. bold. reckless. sometimes necessary.
  • -nostdlibinc — do not search the standard system directories for include files, but do still search the compiler builtin include directories. the middle-ground queen.
  • -nobuiltininc — do not search clang's own builtin directory for include files. bye bestie 🫶
  • -nostdinc++ — do not search the system C++ standard library directory for include files.
  • -fkeep-system-includes — usable only with -E. Instead of copying the preprocessed content of "system" headers to the output, it preserves the #include directive instead. This can greatly reduce the volume of text produced by -E, which is super helpful when you're trying to produce a "small" reproduceable test case. small file, big slay ✨
but listen — this option does not guarantee reproduceability. no cap. If the including source defines preprocessor symbols that influence the behavior of system headers (for example, _XOPEN_SOURCE), then the operation of -E will remove that definition and thus can change the semantics of the included header. Also, using a different version of the system headers (especially a different version of the STL) may result in different behavior. So always verify the preprocessed file by compiling it separately. always. 🚨

🌈 ENVIRONMENT 🌈

the vibes your shell passes down, bestie:

  • TMPDIR, TEMP, TMP — these environment variables are checked, in order, for the location to write temporary files used during the compilation process. first one wins 🏆
  • CPATH — if this environment variable is present, it's treated as a delimited list of paths to be added to the default system include path list. The delimiter is the platform dependent delimiter, as used in the PATH environment variable.

Empty components in the environment variable are ignored. (yes, those :: situations, they just get skipped, no drama)

  • C_INCLUDE_PATH, OBJC_INCLUDE_PATH, CPLUS_INCLUDE_PATH, OBJCPLUS_INCLUDE_PATH — these environment variables specify additional paths, just like CPATH does, except they're only used when processing the appropriate language. so C_INCLUDE_PATH is for C, OBJC_INCLUDE_PATH for Objective-C, CPLUS_INCLUDE_PATH for C++, OBJCPLUS_INCLUDE_PATH for Objective-C++. each one knows its own lane 💜
  • MACOSX_DEPLOYMENT_TARGET — if -mmacos-version-min is unspecified, the default deployment target is read from this environment variable. This option only affects Darwin targets. so if you're not on Darwin this one literally does not care about you 🍎✨

💀 BUGS 💀

found something cursed? it happens to the best of us.

To report bugs, please visit <https://github.com/llvm/llvm-project/issues/>. Most bug reports should include preprocessed source files (use the -E option) and the full output of the compiler, along with information to reproduce. give them the receipts, bestie 🧾 — repro steps are the whole entire point.

🔍 SEE ALSO 🔍

go read these next, they're the supporting cast:

👑 AUTHOR 👑

Maintained by the Clang / LLVM Team (<http://clang.llvm.org>) — absolute icons, keeping the whole thing alive 🫶

2007-2025, The Clang Team — that's the whole legal vibe, periodt.

and that's a wrap on CLANG(1) bestie!! 💖 this page is from Sep 03, 2025, page 20 of the manual, and it's the CLANG(1) page itself (iykyk) — go compile something iconic, you've got this ✨🌸🦋💅

📦 where this page comes from