C and C++ compiler and toolchain for embedded systems and operating systems. One binary targets Arm Cortex-M/A, RISC-V, AVR, Xtensa, TriCore, RX, ColdFire, MIPS, PowerPC, SPARC, LoongArch, x86-64 and AArch64, with its own assembler, linker, debugger and simulator.

Is EmbLinkOs/EmbCC beginner-friendly?

The maintainers of EmbLinkOs/EmbCC usually reply to a pull request within 1 day. 4 beginner-friendly issues are open now.

Stars
1
Forks
2
Open beginner issues
4
Indexed issues
12
Avg merge
20h 55m
Merged PRs (30d)
73
Dominant language
C
License
Apache-2.0
Last GitHub push
Nov 9, 2026
Latest indexed
Nov 10, 2026
Contributing guide
Contributing guide
Code of conduct
No code of conduct
Beginner labels
good first issue

How to contribute to EmbLinkOs/EmbCC

  1. Read the contributing guide first: it says how the maintainers want changes proposed, tested and reviewed.
  2. Your contributions will be published under the project's Apache-2.0 license.
  3. Pick one of the 4 open beginner-friendly issues below and comment that you want to work on it before you start.

Issues somebody may already be working on are listed last. List everything by date

  • avr: code is 1.6 to 1.8 times avr-gcc's size on EmbLinkRTOS's Uno images
    Open
    enhancement

    Difficulty 4/5 3-5 days Newbie friendliness 50/100

    EmbLinkOs/EmbCC#207 ·

    Maintainers usually reply within 1 day

  • docs: a step-by-step first program on EmbSim's micro:bit board
    Open
    documentation good first issue

    Difficulty 3/5 1-2 days Newbie friendliness 82/100

    EmbLinkOs/EmbCC#195 ·

    Maintainers usually reply within 1 day

  • docs: bring the roadmap's "Today" column up to date
    Open
    documentation good first issue

    Difficulty 2/5 1-3 hours Newbie friendliness 82/100

    EmbLinkOs/EmbCC#194 ·

    Maintainers usually reply within 1 day

  • tools: --version on every Emb tool, from src/driver/version.h
    Open
    enhancement good first issue

    Difficulty 4/5 3-5 days Newbie friendliness 55/100

    EmbLinkOs/EmbCC#192 ·

    Maintainers usually reply within 1 day

  • embsim: an unknown --board should list the boards and suggest the closest
    Open
    enhancement good first issue

    Difficulty 2/5 1-3 hours Newbie friendliness 88/100

    EmbLinkOs/EmbCC#191 ·

    Maintainers usually reply within 1 day

  • driver: an unknown --opt= goal should name the valid goals
    Open
    enhancement good first issue

    Difficulty 2/5 1-3 hours Newbie friendliness 83/100

    EmbLinkOs/EmbCC#190 ·

    Maintainers usually reply within 1 day

  • driver: suggest the closest warning for an unknown -W name
    Open
    enhancement good first issue

    Difficulty 4/5 3-5 days Newbie friendliness 72/100

    EmbLinkOs/EmbCC#189 ·

    Maintainers usually reply within 1 day

  • driver: suggest the closest triple for an unknown --target=
    Open
    enhancement good first issue

    Difficulty 3/5 1-2 days Newbie friendliness 85/100

    EmbLinkOs/EmbCC#188 ·

    Maintainers usually reply within 1 day

  • What EmbLinkRTOS needs from EmbCC (tracking)
    Open
    enhancement

    Difficulty 5/5 Over a week Newbie friendliness 25/100

    EmbLinkOs/EmbCC#184 · 1 comment ·

    Maintainers usually reply within 1 day

  • nightly: torture or fuzz failed
    Open

    Difficulty 3/5 1-2 days Newbie friendliness 35/100

    EmbLinkOs/EmbCC#170 · 8 comments ·

    Maintainers usually reply within 1 day

  • avr: errno does not link: __errno_location is not in the C library
    Possibly taken @Firat17aze claimed this today. Open
    bug

    Difficulty 2/5 1-3 hours Newbie friendliness 78/100

    EmbLinkOs/EmbCC#206 ·

    Maintainers usually reply within 1 day

  • avr: inline assembly with lo8()/hi8() cuts symbols longer than 16 characters
    Possibly taken @Firat17aze claimed this today. Open
    bug

    Difficulty 4/5 3-5 days Newbie friendliness 55/100

    EmbLinkOs/EmbCC#205 ·

    Maintainers usually reply within 1 day

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.