-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Polymorphic Memory #83
Comments
Pat, I modified the memory to make it less fragile from #80 . In general for the paper we are referring to the branch 'paper'. This is where we have been doing all the dev work. |
This should probably be resolved with the new assembledADT types. I think constructing an ADT value with a bitvector should work now. |
Can we close this issue? |
I think Pat's issue can easily be resolved by just specifying the instruction type to be the assembledADT type upfront. |
@rdaly525 I'm not sure what declaring an instruction to be an 'assembledADT' means. |
I will test this again and provide a simple example if it fails. |
Now that I am implementing real processors with a von Neumann memory architecture, I am running into a problem with the type associated with memory.
Currently, a memory instance is created with a call like:
where
which means initialize
mem[0]
with anInst
andmem[1]
with aWord(0)
and the rest of memory withWord(0)
.This works but is fragile. Any suggestions on how to handle this?
#20
The text was updated successfully, but these errors were encountered: