The LLVM Project is a collection of modular and reusable compiler and toolchain technologies.
C-Rank Grade: A (Welcoming) - 65/100
External PR Merge Rate: 9%
Response Time: <1h
First Timer Success: 11%
llvm/llvm-project has a recorded first-timer success rate of 10.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in llvm/llvm-project respond to incoming external pull requests in approximately 0.1 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 65.4 places llvm/llvm-project in the A tier.
The external contributor pull request merge rate for llvm/llvm-project is 9.2%, based on public PR activity from non-core contributors.
llvm/llvm-project currently has 63 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in llvm/llvm-project. Reviews community pull requests with focus on project quality.
Discussions in llvm/llvm-project focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/llvm/llvm-project?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 16:00 UTC (16:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 13:00 to 17:00 UTC (13:00 - 17:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (11% approval). Large PRs (>500 lines) take ~0 hours (15% approval). Keep your diff compact for rapid review.
https://godbolt.org/z/YdMdsWqP6 Similar to #230886, frexp can be inlined via expandFrexp, but since code size is larger and it may not always be faster than libcall, expandFrexp should only be used for vector frexp when veclib is not available to avoid poor scalarization codegen.
see #173021 #179434 #179434 added an inline expand for modf in SDAG, given this function's inline expansion is very short, x86 should use this to allow vectorization without veclib. https://godbolt.org/z/dGPav1rqE
If a precision is specified for a %s conversion, a null terminator does not need to be present in the array pointed to by the const char * argument. In src/__support/printf_core/string_converter.h, the printf_core::char_writer() function first calls internal::string_length() and afterward clamps using the precision. The printf_core::wchar_writer() function for %ls does not have the same problem, as it counts the length using an internal::StringConverter capped to converting at most precision characters.
The following code: module m type :: x end type integer, bind(c) :: x end Resulted in this output: fatal internal error: CDEFINED not allowed on this kind of symbol at flang/lib/Semantics/symbol.cpp(506) Fortran::common::die Fortran::semantics::Symbol::SetIsCDefined(bool) Fortran::semantics::AttrsVisitor::SetBindNameOn(Fortran::semantics::Symbol&) Fortran::semantics::DeclarationVisitor::DeclareUnknownEntity(Fortran::parser::Name const&, Fortran::semantics::Attrs) Fortran::semantics::DeclarationVisitor::Post(Fortran::parser::EntityDecl const&) Fortran::semantics::ResolveNamesVisitor::Pre(Fortran::parser::SpecificationPart const&) Fortran::semantics::ResolveNamesVisitor::ResolveSpecificationParts(Fortran::semantics::ProgramTree&) Fortran::semantics::ResolveNames(...) Trunk: https://godbolt.org/z/7qEhnv57j This bug was found by fusion-fuzz
sinh is a sign-preserving function. We currently handle the case where sinh(non-negative) = non-negative, but we do not currently handle the mirror case. If the input to sinh is known to never be non-zero positive (fcPosSubnormal | fcPosNormal | fcPosInf), then the result will also never be non-zero positive (fcPosSubnormal | fcPosNormal | fcPosInf). Ruling out zero can be risky, so we will limit the optimization to just ruling out all non-zero positive classes. The result may still be +0.0 or -0.0. non-positive means any value that is negative (including -0.0) or NaN. non-negative means any value that is positive (including +0.0) or NaN. Tests should be similar to how atan2(y, x) is structured. Be careful around FTPZ/DAPZ (flush to positive zero/denormals are positive zero) since a negative-subnormal input or a negative-subnormal output may become positive zero. You can use the applyInputDenormalMode and applyOutputDenormalMode helpers to assist with handling of denormal modes. Note:
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to llvm/llvm-project, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of llvm/llvm-project acknowledge new external contributions in approximately <1 hour. Out of all submitted pull requests from non-core authors in the last 180-day window, 9.2% were successfully merged into the primary branch.
llvm/llvm-project has a recorded first-timer success rate of 10.7%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~<1 hour. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 65.4 places llvm/llvm-project in the Welcoming tier.
The external pull request merge rate is 9.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, llvm/llvm-project currently has 63 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for llvm/llvm-project are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.