HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
gto76
comp-cpp
C++2015–2015
gto76 / comp-cpp

comp-cpp

Comp Mark I – Simple 4-bit virtual computer

3Distinct people
3Mentions
0Explicit recommenders
344GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Comp Mark I – Simple 4-bit virtual computer

GitHub

Where it is used

No documented product use has been verified yet.

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 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 11:56:56 AM 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 hour3 dated mentions

Observed mentions: 2015-06-18 05:58:07 UTC to 2015-06-18 21:31:20 UTC.

012015-06-18 05:00:00 UTC to 2015-06-18 06:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsJun 18, 05:002015-06-18 06:00:00 UTC to 2015-06-18 07:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-06-18 07:00:00 UTC to 2015-06-18 08:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-06-18 08:00:00 UTC to 2015-06-18 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-06-18 09:00:00 UTC to 2015-06-18 10:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-06-18 10:00:00 UTC to 2015-06-18 11:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-06-18 11:00:00 UTC to 2015-06-18 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-06-18 12:00:00 UTC to 2015-06-18 13:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2015-06-18 13:00:00 UTC to 2015-06-18 14:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJun 18, 13:002015-06-18 14:00:00 UTC to 2015-06-18 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-06-18 15:00:00 UTC to 2015-06-18 16:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-06-18 16:00:00 UTC to 2015-06-18 17:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-06-18 17:00:00 UTC to 2015-06-18 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-06-18 18:00:00 UTC to 2015-06-18 19:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-06-18 19:00:00 UTC to 2015-06-18 20:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-06-18 20:00:00 UTC to 2015-06-18 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-06-18 21:00:00 UTC to 2015-06-18 22:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJun 18, 21:00

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
Jun 18, 05:002015-06-18 05:00:00 UTC2015-06-18 06:00:00 UTC110
Jun 18, 06:002015-06-18 06:00:00 UTC2015-06-18 07:00:00 UTC000
Jun 18, 07:002015-06-18 07:00:00 UTC2015-06-18 08:00:00 UTC000
Jun 18, 08:002015-06-18 08:00:00 UTC2015-06-18 09:00:00 UTC000
Jun 18, 09:002015-06-18 09:00:00 UTC2015-06-18 10:00:00 UTC000
Jun 18, 10:002015-06-18 10:00:00 UTC2015-06-18 11:00:00 UTC000
Jun 18, 11:002015-06-18 11:00:00 UTC2015-06-18 12:00:00 UTC000
Jun 18, 12:002015-06-18 12:00:00 UTC2015-06-18 13:00:00 UTC101
Jun 18, 13:002015-06-18 13:00:00 UTC2015-06-18 14:00:00 UTC000
Jun 18, 14:002015-06-18 14:00:00 UTC2015-06-18 15:00:00 UTC000
Jun 18, 15:002015-06-18 15:00:00 UTC2015-06-18 16:00:00 UTC000
Jun 18, 16:002015-06-18 16:00:00 UTC2015-06-18 17:00:00 UTC000
Jun 18, 17:002015-06-18 17:00:00 UTC2015-06-18 18:00:00 UTC000
Jun 18, 18:002015-06-18 18:00:00 UTC2015-06-18 19:00:00 UTC000
Jun 18, 19:002015-06-18 19:00:00 UTC2015-06-18 20:00:00 UTC000
Jun 18, 20:002015-06-18 20:00:00 UTC2015-06-18 21:00:00 UTC000
Jun 18, 21:002015-06-18 21:00:00 UTC2015-06-18 22:00:00 UTC101

What Hacker News says

3 sources
I wrote a little fibonacci: RAM AD PC ADDR ________ _ _ ---- |---****-|-|*| ---* |----**-*|-|-| --*- |---***--|-|-| --** |--*-***-|-|-| -*-- |---***-*|-|-| -*-* |----**--|-|-| -**- |---*****|-|-| -*** |-*------|-|-| *--- |--------|-|-| *--* |--------|-|-| *-*- |--------|-|-| *-** |--------|-|-| **-- |--------|-|-| **-* |-------*|-|-| ***- |--------|-|-| **** | OUTPUT |-|-| But due to the saturating arithmetic, it gets to 255 and then just prints 255 over and over. I tried to write one that would reset itself when that happens, but I can't seem to do it in 15 bytes (I have a 14 instruction+3 variable version but of course 17 bytes won't fit in RAM) Edit: I can save one of the variables with a set-immediate instruction :) https://github.com/gto76/comp-cpp/pu
Read the rest
In Simple 4-bit/1 Hz virtual computer for learning purposes
And why ADDR_SIZE squared? That just seems to work "by accident", since ADDR_SIZE is 4 it evaluates to 15. What is really meant is probably (1 << ADDR_SIZE), i.e. 2 raised to ADDR_SIZE. Of course for the value 4 it evaluates to the same thing. For 5 it would become 24 rather than 31 which I would expect, assuming it's a size in bits of course ... Now I'm confused. The file in question: https://github.com/gto76/comp-cpp/blob/e800d121e40f8acca6b9d.... And the -1 seems to be explained by how the author wants to use it, it's "last valid address", i.e. not the size at all. Something I'd complain about if this were open for review, for sure. :)
In Simple 4-bit/1 Hz virtual computer for learning purposes

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.