Just for once I did not rush to an online forum and say I had found a bug in a product – and I was right not too. Having tried three different cross compiler toolchains I convinced myself that the issue was plainly neither compiler (or, to be more accurate in this case, assembler) output… Read More Squashing the LRU bug
When I say working, I mean boots into an endless loop with no ouput to the user – but then, that’s what it’s meant to do: Only have to get it to do something useful now, how hard could that be? (There is a linker script to get this to work also – as it… Read More First working assembly code in 33 years
Every programmer will be familiar with something like this… A little while back I wrote a program that simulates – crudely but effectively – a multicore NoC device. I use it to model the execution times of different page replacement algorithms. The input is XML generated via a step by step trace of a working… Read More Curses on ncurses
Paging and virtual memory is at the heart of just about any computing device – more complex than a DVD player – we use everyday. Paging is the memory management system based on the idea that we can divide the real memory of our computer into a sequence of smallish (typically 4,096 bytes) of “page… Read More After paging?
Once you realise what is happening this is obvious, but it took me a while… I wanted to write some longs out as character strings in C++, so wrote some code like this: But compile time error after compile timer error followed as I was told that I could not use this code with unsigned… Read More Passing by reference in C++ – a downside
This is a post about my PhD research: in fact it is a sort of public rumination, an attempt to clarify my thoughts in writing before I take the next step. It’s also possibly an exercise in procrastination: a decision to write about what I might do next, rather than to get on with doing… Read More None of the easy things work
This follows on from the previous post – here are the plots. These are based on a run of the PARSEC benchmark suite x264 program – encoding 32 frames of video using 18 threads – 16 worker threads: the plots show how often each 16 byte “line” is used – whether as an instruction is… Read More Which bit of a 4k page does your program use?