Toggle search
Search
Toggle menu
notifications
Toggle personal menu
Editing
Known issues/2.0.16
From Turing Complete
Views
Read
Edit
Edit source
View history
associated-pages
Page
Discussion
More actions
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
{{Breadcrumbs|Alpha Branch/{{SUBPAGENAME}}}} {{Early-access-version|2|0.16|apha}} A number of levels in version are known to be broken, and require some workarounds to complete. Some of thes issues affect multiple levels, I only give the first level you are likely to come across them. == Symphony Counter == [https://discord.com/channels/828292123936948244/1357725850828673305 Missing bit-width tool and 16-bit] You should be able to place 16-bit components, but the bit-width tool might not be present in the level. Some people report that the bit-width tool appears simply by going to the Sandbox then component factory. If that does not work you can copy-paste 16-bit components from the sandbox. == Wire Spaghetti == [https://discord.com/channels/828292123936948244/1357728243456806984 RAM broken in Wire Spaghetti] Various issues with RAM in Wire Spaghetti and following levels. These stem from the lack of API in <code>text.si</code> to identify which RAM block is the program and which is the register file. '''WORKAROUNDS''': # Copy-paste a 16-bit RAM from sandbox for the register file, then # Copy-paste a 32-bit RAM from sandbox for the program. # These steps should be taken in order. This might take several attempts, for reasons that are unclear to me. [https://discord.com/channels/828292123936948244/1357729558547398837 Wire Spaghetti level log out of date] The level log for Wire Spaghetti states: 3. Click "Edit link components" on the program component and then "Add register file". (do not connect the zr register) This is now wrong, zr should be linked, as part of the register file. === RAM is byte addressed === The level log does not make clear that RAM is byte addressed (this is a change from 0.1059). Since the register file entries are 16-bits (2 bytes) wide the register address should be adjusted to match. === r9 should have value 65535 not 0 === If you see this error on tick 62, then you are writing to and reading from the zero register, this is an error in your circuit, not a bug in the game. == Integrating ALU == The ALU you previous built has a multipy instruction. The tests for Integrating ALU assume mul returns zero. '''WORKARND''': Delete or otherwise disable the multiply componet inside the ALU custom component. == RAM == === The level log is incomplete. === There are 4 new instructions: * <code>store_16</code> * <code>load_16</code> * <code>store_8</code> * <code>load_8</code> The level log incorrectly states put the store port at the top, they should (for this level) be at the bottom. '''WORKAROUND''': Add to the existing program block from bottom to top: # a 16-bit store port, then # an 8-bit store. # Move the existing 32 bit load port above the store ports, followed by # a 16-bit load port, and # an 8-bit load port. == Instruction aliases == === Level fails to compile due to wrong meta.txt === Edit <code>Turing Complete\campaign\symphony_9_aliases\meta.txt</code> and delete the last 4 lines of default_assembly, so that the section reads <pre>default_assembly = ` in r1 mov r2, r1 neg r3, r2 not r4, r2 `</pre> === Level fails due to wrong test.si === Edit <code>Turing Complete\campaign\symphony_9_aliases\test.si</code> and replace the it all with <pre>def get_input($scratch_space: [Int], tick: Int, $inputs: [Int]) { inputs[0] = 10 } def check_output($scratch_space: [Int], tick: Int, inputs: [Int], outputs: [Int]) TestResult { switch tick 0 { if get_register_value(1) != 10 { set_error(`The first instruction is supposed to move the input value (10) to r1.`) return fail } } 1 { if get_register_value(2) != 10 { set_error(`The first instruction is supposed to move the input value (10) to r2.`) return fail } } 2 { if get_register_value(3) != 65526 { set_error(`Negate r2 and store the result (65526) in r3.`) return fail } } 3 { if get_register_value(4) != 65525 { set_error(`NOT r2 and store the result (-9) in r4.`) return fail } return win } }</pre> == Various levels == A number of levels' meta.txt have out of date spec.isa, these can be fixed with a simple regex <pre> s/(^| )([01][01])0/$10$2/g </pre>
Summary:
Please note that all contributions to Turing Complete are considered to be released under the Creative Commons Attribution-ShareAlike (see
TuringComplete:Copyrights
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Templates used on this page:
Template:-
(
edit
)
Template:Breadcrumbs
(
edit
)
Template:Breadcrumbs/styles.css
(
edit
)
Template:Early-access-version
(
edit
)
Template:Tag
(
edit
)
Template:Tag/styles.css
(
edit
)