Figured it out; turns out my code to align the stack so I could make
calls without raising exceptions was messing up and corrupting the
stack-pointer.
Running the -O2 code now makes the clock run a bit too quickly - the
calibration may have a minor issue. I'll fix that up and send patches
tomorrow
Hi!
In the process of cleaning my work up, I've run into an odd problem
which only shows up when I set the optimization level to -O2. At -O0,
it's perfectly fine.
The issue is that somehow execution ends up at address 0x0.
This likely happens due to a _CPU_Context_switch, where the rsp is set
to
On 11/8/18 6:31 am, Gedare Bloom wrote:
> On Fri, Aug 10, 2018 at 2:10 AM, Chris Johns wrote:
>> On 10/08/2018 15:41, Sebastian Huber wrote:
>>> On 10/08/18 07:38, Chris Johns wrote:
On 10/08/2018 15:03, Sebastian Huber wrote:
> we want a ticket for each milestone in which it is resolved.
