ClangBuildAnalyzer
cppcoro
ClangBuildAnalyzer | cppcoro | |
---|---|---|
6 | 24 | |
931 | 3,235 | |
- | - | |
5.7 | 0.0 | |
2 months ago | 4 months ago | |
C++ | C++ | |
The Unlicense | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ClangBuildAnalyzer
-
Speeding up C++ build times
> On another note: C++ compiler should by default keep statistics about the chain of #include's / parsing during compilation and dump it to a file at the end and also summarize how badly you're re-parsing the same .h files during build.
Not exactly that, but do you know clang's -ftime-trace and tools like https://github.com/aras-p/ClangBuildAnalyzer which help analyzing where time is actually spent? (In small repeated headers I don't see much of a problem, but they of course may contain not so small things ...)
-
Build Insights Now Available in Visual Studio 2022
You can also use the following when you want to inspect multiple files: https://github.com/aras-p/ClangBuildAnalyzer
-
IncludeGuardian - improve build times by removing expensive includes
ClangBuildAnalyzer reports on parsing, build, and link time, whereas IncludeGuardian only reports on parsing time.
-
"Fast Kernel Headers" Tree -v1: Eliminate the Linux kernel's "Dependency Hell"
https://github.com/aras-p/ClangBuildAnalyzer is a very useful tool to quantify the cost of different headers (and other costly parts of the compile such as template instantiations). It doesn’t help with actually fixing such problems, but it’s a pretty good ruler to measure where the time is spent.
-
How to understand output of gcc -ftime-report
If you can compile with Clang, I suggest you to try ClangBuildAnalyzer
cppcoro
-
Struggle with C++ 20 Coroutines
PS: Take a look at cppcoro; this might help as well, especially generator<>, if you're looking to generate numbers, and stuff;
-
Does C++23 have a coroutine task promise type?
This is the only viable implementation.
-
Stop Comparing Rust to Old C++
Kind of sounds like whatever library you were using provided leaky abstractions. Something like cppcoro provides really good abstractions for coroutines, the user really doesn't need to understand why any of it works.
-
Sane coroutine imitation with macros; copyable, serializable, and with reflection
Is there a usecase for copying/serializing such coroutines? If not, I would use the normal C++20 coroutines (cppcoro?).
-
Is Tokio::sync::Mutex lock-free?
C++ has the popular CppCoro library. Async_mutex is its equivalent of Tokio::sync::Mutex, providing exclusive access to data shared between tasks.
- My experience with C++ 20 coroutines
-
My thoughts and dreams about a standard user-space I/O scheduler
Because the whole application is running under a single thread there is no need for atomic operations in synchronization primitives(which most of the time requires seq_cst memory order and CMPXCHG which is an expensive instruction in CPU). for example what async_mutex would look like if it knows it's running in a single-threaded scheduler (a non-atomic state variable and waiters queue).
-
[Discussion] What are some old C++ open source projects you wish were still active?
Maybe not old, but I wish cppcoro was still updated. It was such a nice start!
-
A high-level coroutine explanation
You can get generator<> from https://github.com/lewissbaker/cppcoro
-
C++ Coroutines Do Not Spark Joy
It is possible to compose them more easily than described in the article; Lewis Baker's cppcoro library for example provides a recursive_generator<> type[0] that allows this without using any macros. It's up to the library part of coroutines to make things easy, end users are not expected to write low-level coroutine code themselves.
I wonder about the allocation elision. Return value optimization became mandatory, and some compilers can already elide calls to new/delete and malloc()/free() in normal code, so perhaps it will be possible to guarantee allocation elision in the future in the most used cases.
[0]: https://github.com/lewissbaker/cppcoro#recursive_generatort
What are some alternatives?
Bear - Bear is a tool that generates a compilation database for clang tooling.
libunifex - Unified Executors
sol2 - Sol3 (sol2 v3.0) - a C++ <-> Lua API wrapper with advanced features and top notch performance - is here, and it's great! Documentation:
drogon - Drogon: A C++14/17/20 based HTTP web application framework running on Linux/macOS/Unix/Windows
ccache - ccache – a fast compiler cache
Folly - An open-source C++ library developed and used at Facebook.
include-what-you-use - A tool for use with clang to analyze #includes in C and C++ source files
C-Coroutines - Coroutines for C.
simdjson - Parsing gigabytes of JSON per second : used by Facebook/Meta Velox, the Node.js runtime, ClickHouse, WatermelonDB, Apache Doris, Milvus, StarRocks
Flow - Flow is a software framework focused on ease of use while maximizing performance in closed closed loop systems (e.g. robots). Flow is built on top of C++ 20 coroutines and utilizes modern C++ techniques.
zapcc - zapcc is a caching C++ compiler based on clang, designed to perform faster compilations
coproto - A protocol framework based on coroutines