-
Notifications
You must be signed in to change notification settings - Fork 98
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
APPENDTO not respecting slot #628
Comments
Thanks for the report! I'll try to fix this latest on Wednesday this week... |
I think the issue here is that the assembler doesn't to any appending of .SECTIONs or .RAMSECTIONs and reports what is just written in the code. If you link the object containing this code you should see WLALINK doing the appending (here I inserted this code to the code in #630 and got this in the end: What is interesting here that here in the output we have a report about the SLOT where the APPENDTO .RAMSECTION was put initially (0). Found out that it's a bug in WLALINK... linked.sym: Seems like WLALINK appends just fine, it just reports a bit wrong... |
I could also try to make the assembler sniff around the code and report in your case correctly what is going to happen... unless linkfile for WLALINK specifies a new slot/bank for these .RAMSECTIONs, then the assembler would be wrong. :) |
great thanks :) Yes it looks like with the latest version, |
A somewhat related feature request, would it be desirable/possible at some point to implement an optional |
DEFAULTRAMSLOT sounds like a useful feature so I'll try to implement it later this week |
Hi there,
It looks like appending data to another RAMSECTION doesn't append it to the same slot.
The above results in wla-z80 mapping the following:
I would expect it to append to the same slot and bank, but is the current behaviour intentional? It seems even if I change
defaultslot
to another value it still goes to slot 0. Assigning the slot in theappendto
section results in it mapping as I'd expect. I haven't seen this issue with sections so I'm not sure if those are affected as well.EDIT: It looks like it does affect sections too
The text was updated successfully, but these errors were encountered: