Embedded Linker (eld)
C-Rank Grade: S (Elite) - 75/100
External PR Merge Rate: 71%
Response Time: 12h
First Timer Success: 72%
qualcomm/eld has a recorded first-timer success rate of 72.2%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in qualcomm/eld respond to incoming external pull requests in approximately 12.2 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 75.1 places qualcomm/eld in the S tier.
The external contributor pull request merge rate for qualcomm/eld is 71.2%, based on public PR activity from non-core contributors.
qualcomm/eld currently has 9 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in qualcomm/eld. Prompt code reviews with positive guidance for new contributors.
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/qualcomm/eld?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 20:00 UTC (20:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 18:00 to 22:00 UTC (18:00 - 22:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~8 hours (89% approval). Large PRs (>500 lines) take ~59 hours (32% approval). Keep your diff compact for rapid review.
On ARM/AArch64 --save-temps unexpectedly changes LTO from native object emission to assembly emission and causes invocation of external assembler. A diagnostic option such as --save-temps should not result in changing the linker/compiler/lto flow. Reproducer: #!/usr/bin/env bash set -x mkdir -p tmp cat > tmp/lto-aarch64-save-temps.c <<\EOF void _start(void) {} EOF cat > tmp/clang <<\EOF #!/usr/bin/env bash exit 99 EOF chmod +x tmp/clang clang --target=aarch64-linux-gnu -flto -c tmp/lto-aarch64-save-temps.c -o tmp/lto-aarch64-save-temps.bc ld.eld -march aarch64 -e _start tmp/lto-aarch64-save-temps.bc -o tmp/lto-aarch64-save-temps.normal.eld.out PATH=tmp:$PATH ld.eld -march aarch64 --save-temps -e _start tmp/lto-aarch64-save-temps.bc -o tmp/lto-aarch64-save-temps.saved.eld.out Output: Note: LTO generated bitcode: tmp/lto-aarch64-save-temps.saved.eld.out.llvm-lto.* Note: Using 8 threads for LTO code generation. Fatal: LTO: Assembler error occurred Fatal: Linking had errors (lto-aarch64
LLVM only supports -O0 to -O3. If values above this are used, then LLVM reaches llvm_unreachable and causes the link to crash. #!/usr/bin/env bash set -x mkdir -p tmp cat > tmp/lto-o4.c <<\EOF void _start(void) {} EOF clang --target=x86_64-linux-gnu -flto -c tmp/lto-o4.c -o tmp/lto-o4.o ld.eld -m elf_x86_64 --lto-O4 -e _start tmp/lto-o4.o -o tmp/lto-o4.eld.out ld.lld -m elf_x86_64 --lto-O4 -e _start tmp/lto-o4.o -o tmp/lto-o4.eld.out lld properly reports invalid optimization error, whereas eld crashes.
cat > 1.c << \! int foo() { return 0; } ! clang -c 1.c tar cvf a.tar 1.o ld.bfd a.tar ld.eld a.tar We would like to recognize it is tar file and report an error.
Windows https://github.com/qualcomm/eld/actions/runs/36805262162/job/110188068094 Summarizing ELD lit test results across all configurations Configuration PASS FAIL XFAIL UNSUPPORTED XPASS TIMEOUT TOTAL TIME ---------------------------------------------------------------------------------------- arm-default 1409 0 2 1127 0 0 2538 1m32.1s aarch64-default 1304 0 2 1232 0 0 2538 1m22.4s riscv-default 1225 0 0 1313 0 0 2538 1m17.6s hexagon-default 1638 0 1 899 0 0 2538 1m32.0s x86-default 829 0 0 1709 0 0 2538 55.8s riscv64-default 1203 0 0 1335 0 0 2538 1m16.5s x86_32-default 4 0 0 0 0 0 4 0.4s Linux https://github.co
cat > 1.c << \! int foo() { return 0; } ! $clang -c 1.c $ld.eld 1.o $readelf -p .comment a.out String dump of section '.comment': [ 1] clang version 24.0.0git (https://github.com/llvm/llvm-project/ c6b15d38928d586064932c3cc26d8c777e104196) [ 6a] Linker 24.0 (ebf1402400117e162c88ceb893a7cdac1f67dcc9) [ a2] LLVM 24.0.0git (c6b15d38928d586064932c3cc26d8c777e104196) $ld.lld 1.o $ readelf -p .comment a.out String dump of section '.comment': [ 1] Linker: LLD 24.0.0 (https://github.com/llvm/llvm-project/ c6b15d38928d586064932c3cc26d8c777e104196) [ 65] clang version 24.0.0git (https://github.com/llvm/llvm-project/ c6b15d38928d586064932c3cc26d8c777e104196) It would be useful to produce lld style output and make it easy to recognize that eld is used when linking with eld.
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 qualcomm/eld, 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 qualcomm/eld acknowledge new external contributions in approximately 12 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 71.2% were successfully merged into the primary branch.
qualcomm/eld has a recorded first-timer success rate of 72.2%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~12 hours. 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 75.1 places qualcomm/eld in the Elite tier.
The external pull request merge rate is 71.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, qualcomm/eld currently has 9 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for qualcomm/eld 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.