# Request for an integrated C compiler for binary patching

**URL:** <https://community.hex-rays.com/t/request-for-an-integrated-c-compiler-for-binary-patching/318>\
**Category:** IDA General\
**Created:** [May 12, 2025, 3:39pm UTC](https://community.hex-rays.com/t/request-for-an-integrated-c-compiler-for-binary-patching/318 "2025-05-12T15:39:42Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![void\_17](https://avatars.discourse-cdn.com/v4/letter/v/d2c977/32.png) [@void\_17](https://community.hex-rays.com/u/void_17)\
**Post date:** [May 12, 2025, 3:39pm UTC](https://community.hex-rays.com/t/request-for-an-integrated-c-compiler-for-binary-patching/318/1 "2025-05-12T15:39:42Z")

</div>

Hello! I would like to request a feature that is similar to what’s already present in another reverse engineering tool, Binary Ninja. It’s called a [shellcode compiler](https://scc.binary.ninja/) and it allows to patch the existing binary code with a higher level language compared to raw assembly, and the language is C. This built-in feature is an amazing tool for binary patching the existing binary when you have no room for dynamic binary patching. It proved its usefulness for me and I want to see it in the next releases of IDA. Thanks!

Regards, void\_17.

---

<div class="post-metadata">

**Author:** ![pag](https://sea2.discourse-cdn.com/flex002/user_avatar/community.hex-rays.com/pag/32/54_2.png) [@pag](https://community.hex-rays.com/u/pag)\
**Post date:** [May 12, 2025, 5:04pm UTC](https://community.hex-rays.com/t/request-for-an-integrated-c-compiler-for-binary-patching/318/2 "2025-05-12T17:04:50Z")

</div>

Have you considered making an IDA plugin for Binary Ninja’s shellcode compiler? It appears to be open-source: [GitHub - Vector35/scc](https://github.com/Vector35/scc).

---

<div class="post-metadata">

**Author:** ![vadimbrk](https://avatars.discourse-cdn.com/v4/letter/v/b9e5f3/32.png) [@vadimbrk](https://community.hex-rays.com/u/vadimbrk)\
**Post date:** [May 17, 2025, 7:01pm UTC](https://community.hex-rays.com/t/request-for-an-integrated-c-compiler-for-binary-patching/318/3 "2025-05-17T19:01:39Z")

</div>

And the api won’t be obsolete in the next version? My main issue with ida is the lack consistency. Plenty of good working plugins that’s just don’t work without modifications due to api changes

---

<div class="post-metadata">

**Author:** ![teresa\_hexrays](https://sea2.discourse-cdn.com/flex002/user_avatar/community.hex-rays.com/teresa_hexrays/32/11_2.png) [@teresa\_hexrays](https://community.hex-rays.com/u/teresa_hexrays)\
**Post date:** [May 20, 2025, 11:53am UTC](https://community.hex-rays.com/t/request-for-an-integrated-c-compiler-for-binary-patching/318/4 "2025-05-20T11:53:47Z")

</div>

Hello @vadimbrk,  
We understand the concerns around API changes. As our product evolves, the API needs to evolve with it. Some of the recent changes were necessary to improve overall usability and were made with consideration, including feedback from our users. That’s why we added new helper endpoints along with [examples](https://docs.hex-rays.com/developer-guide/idapython/idapython-examples) to make the transition as smooth as possible.

With the release of IDA 9.0, we introduced a few major changes—documented in the porting guides—that may require adjustments for plugin authors. However, this level of change is not something we plan to repeat in every release. In fact, these recent updates were designed to simplify the experience with our API and reduce the need for disruptive changes in the future.

If you run into any issues while porting your plugins, feel free to post here—we’ll try to help and give you some tips.