#Expand Instructions Area?

1 messages · Page 1 of 1 (latest)

dusky garnet
#

The Instructions window only really provides an instruction guide for up to 8 bits; I think it could be very helpful to have a dropdown for allowing guidelines to be set for different bit numbers (ie. 16, 32, 64). Thoughts?

rough monolith
#

yes, this is an obvious improvement, and people mentioned it before multiple times (before the "feature request" forum was there)

deep portal
#

I suggest making it so that there is an option so that: A) You can define several rulesets (E.X. Define a ruleset for arguments, output locations, and commands) and B) You can have a command that forces some bits of the arguments to be true or takes multiple bytes. Another idea is a small parser that lets you say something like 0b11aabb01 aaaabbbb bbbbaaaa cccccccc where a, b, and c would be substituted somehow.

torn pendant
#

not having this is the main thing keeping me from using data widths higher than 8-bit rn (tracking the rules by hand is painful lol)

gleaming fog
#

My current project has wide instructions, but I don't need to care what bit-patterns they are (except for the top bit) as I use a ROM microcode lookup to drive the result.

sinful shoal
#

Maybe even multiples of 8?

#

Like a 24 bit instruction area.

mellow barn
torn pendant
frigid vale
#

Yeah we used customasm in #etc-architecture before deciding we could do better with our own assembler written in python and then just did that

#

(we've since ported GAS, but this is a lot of work and not an acceptable workaround for most people doing projects/experiments with new ISAs)

gleaming fog
#

I used a simple c# program to create my ROM contents and it also output it as a program, but having 2 program components isn't quite supported.

deft flume
frigid vale
#

My last post in show and tell is using two and I never had a problem

olive summit