| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |
|
|
|
|
|
|
| |
This can happen with
CCACHE_LOGFILE=/dev/stdout ccache compiler ... |& head -n 1
or similar.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
This is the next step after a57f70eda32e99221de56f5499079b4f00dc2bc5.
|
| | |
|
| |
|
|
|
|
| |
some 32bit architectures e.g. RISCV32 use 64bit time_t from beginning
which does not fit into long int size on LP32 systems
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
| |
|
|
| |
See also 4413d842e23c6fa52ec411951a4ab442f42227de.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
fmtlib can detect format string errors at compile time if (1) applying
FMT_STRING to the format string literal and (2) compiling for C++14 or
higher.
Requirement 1 is implemented by introducing a LOG macro which applies
FMT_STRING to the first argument and calls Logging::log (if logging is
enabled). Also added are a companion LOG_RAW macro (since C++11 requires
at least one argument for the “...” part in variadic macros) and a
BULK_LOG macro which calls Logging::bulk_log (if logging is enabled).
Requirement 2 is implemented by setting CMAKE_CXX_STANDARD to 14 for one
CI build with a known C++14-capable compiler. We can’t set it to 14 by
default since we still want the code to be buildable with C++11
compilers.
This will catch errors such as the one fixed by PR #691.
|
| | |
|
| |
|
|
|
| |
This makes the naming more consistent with the other exception classes
(Error and Failure).
|
| |
|
|
|
| |
I think that this improves code readability since it’s more clear what
the code flow is.
|
| | |
|
| | |
|
|
|
- Simplified and C++-ified logging code.
- Added Logging::log and Logging::bulk_log functions corresponding to
the old cc_log and cc_bulklog functions. The new functions pass their
arguments to fmt::format.
- Replacements:
* init_log → Logging::init
* cc_log → Logging::log
* cc_bulklog → Logging::bulk_log
* cc_log_argv → Logging::log plus Util::format_argv_for_logging
* cc_dump_debug_log_buffer -> Logging::dump_log
- A legacy cc_log implementation is still available so that logging can
be converted gradually to the new functionality.
|