I'm compiling LLVM as well as clang. I noticed that the output of compilation has llvm[1]:
or llvm[2]:
or llvm[3]
: prefixed to each line. What do those integers in brackets mean?
相关问题
- CMakeList file to generate LLVM bitcode file from
- AddressSanitizer blacklist in c++ not working
-
Apple Clang and numeric_limits
::max() is - Why clang missing default argument on parameter pa
- LLVM OPT not giving optimised file as output.
相关文章
- How do I generate an AST from a string of C++ usin
- clang error: non-type template argument refers to
- Makefile: all vs default targets
- Swift and Objective-c framework exposes its intern
- Automake Variables to tidy up Makefile.am
- Compiling a .C file: Undefined symbols for archite
- (Optimization?) Bug regarding GCC std::thread
- What does Clang's 'type_visibility' at
The currently accepted answer is not correct. Furthermore, this is really a GNU Make question, not a LLVM question.
What you're seeing is the current value of the
MAKELEVEL
variable echoed bymake
to the command line. This value is set as a result of recursive execution. From the GNU make manual:If you have a copy of the GNU Make source code on hand, you can see your output message being generated in
output.c
with thevoid message(...)
function. In GNU make v4.2, this happens on line 626. Specifically theprogram
argument is set to the string "llvm" and the makelevel argument is set as noted above.Since it was erroneously brought up, it is not the number of the compilation job. The
-j [jobs]
or--jobs[=jobs]
options enable parallel execution of up tojobs
number of recipes simultaneously. If-j
or--jobs
is selected, butjobs
is not set, GNU Make attempts to execute as many recipes simultaneously as possible. See this section of the GNU Make manual for more information.It is possible to have recursive execution without parallel execution, and parallel execution without recursive execution. This is the main reason that the currently accepted answer is not correct.
It's the number of the compilation job (
make -j
). Helpful to trace compilation errors.Apparently, it's not connected to the number of the compilation job (can be easily checked via make -j 1). The autoconf-based build system indicates the "level" of the makefile inside the source tree). To be prices, it's a value of make's MAKELEVEL variable.