HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
avast
retdec
C++2017–2025
avast / retdec

retdec

RetDec is a retargetable machine-code decompiler based on LLVM.

12Distinct people
13Mentions
0Explicit recommenders
8.7KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

RetDec is a retargetable machine-code decompiler based on LLVM.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 10:49:33 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year13 dated mentions

Observed mentions: 2017-12-12 18:53:31 UTC to 2025-01-04 22:22:33 UTC.

0123452017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 5 mentions; 2 submissions, 3 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC523
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC101
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC211
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC110
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC211
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC000
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC101

What Hacker News says

2 sources
sargstuff·Apr 11, 2022Submission

Literal Hands on Coding Method(s)?

Anyone tried modifying the AST-tree of a compiler for a given program(s) in VR space? Is this a viable method for remote office code reviews? Example working concept [1] would be comparing "old" K&R C / C89 vs. port to "modern" C. aka Virtual chalk board in VR 2 or 3D to support video conference. [1] "Old C code -- how to upgrade it?" https://news.ycombinator.com/item?id=30957273#30962540 Concept example: Given "old" c code line of : (--(char)hash_ptr.parm.v.p) = fpop(sst); A) "traditional method": run it through the compiler/debugger, "compile/debug/pray resolve all issues) B) Advanced method: Assuming the license terms on the working binary allows decompilation; 1) Use a disassembler to psudo C on the original binary and same hardware. 2) Diff the resulting pseudo source code to see where things get interpreted differently.
Read the rest
3) Then use combination of "tree differ" ([2]) and compiler explorer to review the "differences", ([3]) C) Next setup up approach: 1) open source decompile to pseudo-C software: ghidra [4]; retdec [5] compiler ware: gcc -fdump-translation-unit or clang -ast-dump 2) Then use something graphbiz's dotty in conjunction with [6] nicst's tree diff util. D) Current, everything but the kitchen sink approach: Almost verything but the VR aspect, Non-free software for non-vr space ast idea: http://www.semdesigns.com/Products/DMS/DMSToolkit.html Query: Is there an open source interactive VR "full compiler stack" tree visualization, so one can "hand manipulate"/ move in/out of compile AST new code or color code diffs between old/new code and/or versions all in 3d? Resources: [2] ast tree diff utils : https://github.com/syntax-tree/awesome-syntax-tree [3] compiler explorer : https://godbolt.org/z/v4TdvE83b [4] ghidra: ghidra-sre.org [5] retdec: https://github.com/avast/retdec [6] nicst utils : https://github.com/syntax-tree/awesome-syntax-tree
1 points · Open discussion
Assuming the license terms on the working binary allows decompilation; could use a disassembler to psudo C on the original binary and same hardware, new 32 bit compile (ideally with same compiler (gcc/clang/etc) used on original binary) Diff the resulting pseudo source code to see where things get interpreted differently. Then use compiler explorer on the "differences", https://godbolt.org/z/v4TdvE83b open source decompile to pseudo-C: ghidra: ghidra-sre.org retdec: https://github.com/avast/retdec
In Old C code – how to upgrade it?

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.