frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Prevalence of chronic traumatic encephalopathy at death in NFL players

https://www.bmj.com/content/394/bmj-2026-100418
1•speckx•2m ago•0 comments

WhatsApp rolls out multi-device passkeys to kill SS7 and SIM Swapping attacks

https://cyberupdates365.com/whatsapp-security-update-2026-passkeys/
2•sysadmin_diarie•2m ago•0 comments

Release v0.2.0 · ggml-org/llama.cpp

https://github.com/ggml-org/llama.cpp/releases/tag/v0.2.0
1•kyisaiah47•3m ago•0 comments

Show HN: RIP MY BUILD, a cemetery for failed side projects

https://www.ripmybuild.com
2•horiajurcut•4m ago•0 comments

Show HN: Turn any website into a CLI for AI agents (142x fewer tokens than HTML)

https://github.com/only-cli/oc
1•hyes•5m ago•0 comments

Two planned datacentres will have higher UK carbon emissions than ExxonMobil

https://www.theguardian.com/uk-news/2026/aug/25/planned-datacentres-carbon-emissions-uk-exxonmobil
1•sbulaev•5m ago•0 comments

Wrapping a callable in a lambda that just calls it with the same parameters

https://devblogs.microsoft.com/oldnewthing/20260819-00/?p=112624
1•ibobev•5m ago•0 comments

How the search for one court record became a nationwide movement

https://www.courtwatch.news/p/the-rabbit-hole-how-the-search-for-one-court-record-became-a-nation...
1•Kye•6m ago•0 comments

Reducing C++ template bloat by factoring out the type-dependent portions

https://devblogs.microsoft.com/oldnewthing/20260821-00/?p=112632
1•ibobev•6m ago•0 comments

OpenAI JalapeñO: Better Than Nvidia Blackwell

https://newsletter.semianalysis.com/p/openai-jalapeno-better-than-nvidia
3•bmulholland•6m ago•0 comments

Fewer, smaller eggs are the double effect of France's scorching summer

https://www.lemonde.fr/en/economy/article/2026/08/25/the-hens-suffocated-fewer-smaller-eggs-are-t...
1•geox•6m ago•0 comments

Comparing the two holograms on the Windows 95 box

https://devblogs.microsoft.com/oldnewthing/20260824-00/?p=112643
1•ibobev•7m ago•0 comments

Read your writes: WAIT FOR in PostgreSQL 19

https://clickhouse.com/blog/postgresql-19-wait-for-read-your-writes
1•gulcin•7m ago•0 comments

AI assistants need adaptive conversational tempo to be good cognitive companions

https://woventhought.substack.com/p/ai-assistants-need-adaptive-conversational
2•ssivark•10m ago•0 comments

How Arlington National Cemetery Came to Be

https://www.smithsonianmag.com/history/how-arlington-national-cemetery-came-to-be-145147007/
2•goles•10m ago•0 comments

Anthropic tells staff to work from home due to possible security team strike

https://www.businessinsider.com/anthropic-san-francisco-staff-work-remote-office-security-strike-...
5•DGAP•12m ago•0 comments

US Military Transport Plane Lands in Moscow After Flight from Riga

https://www.kyivpost.com/post/83088
2•bushwart•12m ago•0 comments

Kafka-free reliably OpenTelemetry ingestion

https://clickhouse.com/blog/reliable-opentelemetry-ingestion-at-scale
1•gingenio•12m ago•0 comments

Apple's M6 Mac mini jumps to $899 as Mac Studio goes Ultra

https://forgeeks.net/apple-m6-mac-mini-m5-ultra-studio/
2•kuuuzya•14m ago•0 comments

Show HN: Unbox-AI Visualize your AI traces like a JavaScript bundle

https://github.com/tester-army/unbox-ai
2•okwasniewski•14m ago•0 comments

A New Framework for How the Brain Compresses Our Noisy World

https://www.quantamagazine.org/a-new-framework-for-how-the-brain-compresses-our-noisy-world-20260...
1•Brajeshwar•15m ago•0 comments

The bond market isn't panicking, it's repricing for a riskier world

https://www.capitaleconomics.com/blog/bond-market-isnt-panicking-its-repricing-riskier-world
2•toomuchtodo•15m ago•0 comments

The Info War Stack: The three layers states are building to win an info war

https://pplsartofwar.substack.com/p/the-info-war-stack
1•iamnothere•16m ago•0 comments

AI Coding Has Erased the Supposed Advantage of Statically Typed Languages

https://yyhh.org/blog/2026/08/ai-coding-has-erased-the-supposed-advantage-of-statically-typed-lan...
3•yogthos•16m ago•0 comments

Show HN: MyPRs – your open-source resume, built from your merged pull requests

https://www.myprs.dev
2•kishanhitk•16m ago•0 comments

SubCost – See what your subscriptions cost over 10 years

https://subcost.surge.sh/
1•paulsassistant•17m ago•0 comments

Exploring 1-Bit LLMs

https://thejeshgn.com/2026/08/25/exploring-1-bit-llms/
1•speckx•17m ago•0 comments

Munich Court Proposes €1.05 Monthly Codec Royalty for Netflix Premium Users

https://streaminglearningcenter.com/articles/munich-court-proposes-e1-05-monthly-codec-royalty-fo...
1•cisc•18m ago•0 comments

What 219 AI evals job postings that publish a salary pay

https://aievalsjobs.com/ai-evals-salary-report/
1•willhannay•18m ago•0 comments

Show HN: Open-source AMDGCN kernels for optimizing LLM inference

https://github.com/NetraRuntime/netra-kernel
2•rbisri•18m ago•0 comments
Open in hackernews

Ask HN: Help with doing statistics over machine code

2•phafu•1y ago
I'd like to do some statistics over the machine code gcc generates, such as a histogram of used instructions, average volatile/preserved registers usage of functions etc. For now just x86_64 SysV-ABI would be enough.

However I'm not aware of any pre-existing tool that lets me easily do this. The options I currently see are either make gcc output assembly and write a parser for the GNU Assembler format (possibly by reusing the asm-parser of the compiler-explorer project), or write a tool that reads (disassembles) object files directly using elfutils.

Any hints, prior work, further ideas, links to useful resources, or any other kind of help would be much appreciated.

Comments

baobun•1y ago
"Static analysis" should be a relevant search term. Assuming you don't need to tie the instructions back to C code then the "gcc" part seems circumstancial for implementation? I guess you might want to parse the ASM into an Abstract Syntax Tree (AST) represenation and work on that?

If you do want to tie it back to the source, this looks relevant: http://icps.u-strasbg.fr/~pop/gcc-ast.html

phafu•1y ago
For my purpose I don't need to get back to the original source, no.

The gcc part is only relevant with regards to what dialect of assembler I need to parse. If I go that route, I'd write a parser for the GNU assembler, and that would of course work with any code in that dialect, regardless from which compiler it came from (I haven't checked whether other compilers can produce GNU assembler though).