0 Members and 1 Guest are viewing this topic.
As the Axe documentation says, you cannot use L₂ in a program run from Mirage.
Quote from: jacobly on December 05, 2012, 11:57:05 amAs the Axe documentation says, you cannot use L₂ in a program run from Mirage.Isn't it possible if interrupts are turned off (FnOff) ?
MirageOS uses parts of L2 for it's data as well, so even if you disable interrupts, you will still be messing with MirageOS vars and weird stuff may happen after you exit.
Quote from: Builderboy on December 05, 2012, 01:17:53 pmMirageOS uses parts of L2 for it's data as well, so even if you disable interrupts, you will still be messing with MirageOS vars and weird stuff may happen after you exit.So would the best option then be to use {L1+100} instead of L2?
If you have less then 600 (and some more , i think 667?) to store, then yes use L1+100
Figured out that I couldn't do this: 0→{L1}→{L1+1}→{L1+2}, derp
Quote from: Derf321 on December 05, 2012, 09:38:53 pmFigured out that I couldn't do this: 0→{L1}→{L1+1}→{L1+2}, derp Yeah, in fact, 0→{L1} returns L1, not 0 so you are actually doing L1→{L1+1} at the second arrow.What you can do is Fill(L1,3,0), which would put zeros in the firts three bytes of L1, which is what you want
Quote from: stevon8ter on December 05, 2012, 04:42:24 pmIf you have less then 600 (and some more , i think 667?) to store, then yes use L1+100The "true" L1 is 768 bytes, but you have the 27 variables at the end of it (A,B,...Z and theta), each of them are 2 bytes, so the available size in L1 is 768-(27*2) (As the Commands.html says, it can be expanded to 768 using Realloc, which would move the variables elsewhere than in L1+714)
Quote from: Hayleia on December 06, 2012, 01:18:02 amQuote from: stevon8ter on December 05, 2012, 04:42:24 pmIf you have less then 600 (and some more , i think 667?) to store, then yes use L1+100The "true" L1 is 768 bytes, but you have the 27 variables at the end of it (A,B,...Z and theta), each of them are 2 bytes, so the available size in L1 is 768-(27*2) (As the Commands.html says, it can be expanded to 768 using Realloc, which would move the variables elsewhere than in L1+714)* Runer112 points to Axe 1.2.0 changelog
Quote from: Derf321 on December 05, 2012, 09:38:53 pmFigured out that I couldn't do this: 0→{L1}→{L1+1}→{L1+2}, derp Yeah, in fact, 0→{L1} returns L1, not 0 so you are actually doing L1→{L1+1} at the second arrow.What you can do is Fill(L1,3,0), which would put zeros in the firts three bytes of L1, which is what you want Quote from: stevon8ter on December 05, 2012, 04:42:24 pmIf you have less then 600 (and some more , i think 667?) to store, then yes use L1+100The "true" L1 is 768 bytes, but you have the 27 variables at the end of it (A,B,...Z and theta), each of them are 2 bytes, so the available size in L1 is 768-(27*2) (As the Commands.html says, it can be expanded to 768 using Realloc, which would move the variables elsewhere than in L1+714)
Author
Topic: Cannot compile my program into a shell? (SOLVED) (Read 5488 times)
