Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
if you *do* have to use a ROM, you could make a multi-tick system where first you read the correct instruction into registers (which can take 1-2 ticks if you are trying to emulate 4 byte program output with 64bit ROM output, or up to 4 ticks if you are outputting a single byte/word per tick), and only when that completes start executing that instruction
thd c0 (make a thread for core #0)
(program)
end
and it would copy the code into the ram of the core.
The center of my issue is that I need to read and write from a ram's memory from a program, and if I use a multi-tick system, then it would ruin the performance reasons for making a multi threaded system. I could technically solve this issue if I made all instructions 4 numbers long, and set the ram to 256-bit mode, however, this would turn the above code into:
thd c0 _ _
(program)
end _ _ _
and bring the count of numbers from 3 to 8, which is a significant gate cost. I will likely do this if it turns out to be the only way, but I would like to see if there is a better alternative.