New pages
- 09:30, 12 March 2019 Msg/DevGpio (hist | edit) [3,063 bytes] Henry (talk | contribs) (Created page with "This page is about the warning messages that can are produced by the GPIO I/O devices. On the Altera University Program computer systems, the same GPIO device is used for swit...")
- 08:29, 11 March 2019 Msg/FunctionNestCount (hist | edit) [2,364 bytes] Henry (talk | contribs) (Created page with "A function is called from a caller, runs some code, and then returns to its caller. Although a function may call other functions (possibly recursively), it is unusual for the...")
- 06:55, 11 March 2019 Msg/FetchSelfModifyingCode (hist | edit) [4,346 bytes] Henry (talk | contribs) (Created page with "Normally, the CPU should execute code that came from an executable file generated by an assembler or compiler. Normally, this code shouldn't be changed at runtime by directly...")
- 06:26, 11 March 2019 Msg/FetchBadPC (hist | edit) [2,715 bytes] Henry (talk | contribs) (Created page with "Normally, the CPU should execute code that came from a code section (such as <code>.text</code>) from an executable file generated by an assembler or compiler. This message te...")
- 05:33, 11 March 2019 Msg/MemoryNoDevice (hist | edit) [1,966 bytes] Henry (talk | contribs) (Created page with "The computer system has a 32-bit address space (addresses are 32 bits, and there is 2<sup>32</sup> bytes = 4 gigabytes of address space), but usually only part of that space a...")
- 05:01, 11 March 2019 Msg/MemoryCacheBypass (hist | edit) [2,392 bytes] Henry (talk | contribs) (Created page with "Memory accesses to memory-mapped I/O should not be cached (or the devices will not see the memory access), while accesses to regular memory should be cached (cache consistency...")
- 07:02, 10 March 2019 Msg/MemoryStackRedZone (hist | edit) [2,641 bytes] Henry (talk | contribs) (Created page with "A stack frame is a region of memory used by an executing function. The memory region at or above the stack pointer is allocated stack space that may be used, while addresses l...")
- 06:44, 10 March 2019 Msg/StackDeallocatedParentFrame (hist | edit) [3,864 bytes] Henry (talk | contribs) (Created page with "A stack frame is a region of memory used by an executing function. When calling a function, the child function's stack frame is at a lower address than the caller's stack fram...")
- 06:22, 10 March 2019 Msg/IntrClobberedRegs (hist | edit) [1,150 bytes] Henry (talk | contribs) (Created page with "An interrupt handler should not modify any registers that are used outside an interrupt context (e.g., et on Nios II), because interrupts can occur at any time. Clobbering a r...")
- 06:16, 10 March 2019 Msg/IntrClobberedRA (hist | edit) [704 bytes] Henry (talk | contribs) (Created page with "An interrupt should normally return to the instruction that was interrupted. This message tells you that this didn't happen: the function return is returning somewhere other t...")
- 06:14, 10 March 2019 Msg/IntrClobberedSP (hist | edit) [844 bytes] Henry (talk | contribs) (Created page with "An interrupt handler should always ensure that the stack pointer and some control registers are the same at the entry and exit of the function. This message tells you that thi...")
- 05:47, 10 March 2019 Msg/MemoryMisaligned (hist | edit) [1,909 bytes] Henry (talk | contribs) (Created page with "Memory accesses need to be aligned. The memory address must be a multiple of the size of the access. For example, a 4-byte load must use an address that is a multiple of 4 byt...")
- 05:02, 10 March 2019 Msg/ClobberedRegs (hist | edit) [2,092 bytes] Henry (talk | contribs) (Created page with "A calling convention defines which registers a function is allowed to modify (caller-saved), and which registers a function should preserve (callee-saved). Clobbering a regist...")
- 01:11, 10 March 2019 Msg (hist | edit) [136 bytes] Henry (talk | contribs) (Created page with "This is a collection of explanations for some of the CPUlator warning messages.") originally created as "Msg/"
- 01:07, 10 March 2019 Msgs (hist | edit) [0 bytes] Henry (talk | contribs) (Created blank page)
- 01:01, 10 March 2019 Msg/ClobberedRA (hist | edit) [2,421 bytes] Henry (talk | contribs) (Created page with "A function should normally return to the instruction after the call instruction in the caller that called this function. This message tells you that this didn't happen: the fu...") originally created as "Msgs/ClobberedRA"
- 23:11, 9 March 2019 Msg/ClobberedSP (hist | edit) [2,494 bytes] Henry (talk | contribs) (Created page with "A function should always ensure that the stack pointer is the same at the entry and exit of the function. This message tells you that this didn't happen: the stack pointer was...")