Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Updated for 2016. | David Thomas | 2016-10-10 | 3 | -48/+23 |
| | |||||
* | Example of how mips_cpu_set_debug_level could be used. | David Thomas | 2014-10-23 | 1 | -0/+38 |
| | |||||
* | Added a much more description on what the memory interface is, and how block ↵ | David Thomas | 2014-10-23 | 1 | -0/+70 |
| | | | | sizes are involved. | ||||
* | Fixed #10: The documentation had an awkward blend of pseudo-code and real code, | m8pple | 2014-10-21 | 1 | -2/+4 |
| | | | | | | which never helps. Changed to be real code. (Deliberately kept the error checking though). | ||||
* | Fixed #7: Documented state parameter as non-empty | m8pple | 2014-10-21 | 1 | -1/+3 |
| | | | | | | | | | | | | | | Note that I would not really consider this as a backwards compatibility problem, as there is a documented way of returning error codes, and an error code exists for this situation. One would expect any reasonable implementation to check for non-null as a sanity check, as it so cheap. The exception would be if it was documented as a performance critical method (which it is, but we don't care about performance), where you would probably either put a blanket warning "No pre-conditions will be checked" for the module, or ideally on just the performance critical functions. | ||||
* | Fixed #8 : Added the documentation for mips_cpu_get_pc (oversight on my part). | m8pple | 2014-10-21 | 1 | -2/+8 |
| | | | | | | | I didn't add constraints on the pointer validity, as they are covered under a more common sense argument. There is no reasonable interpretation for passing a null or invalid pointer for pc, as it cannot give the caller any more information than they already have. | ||||
* | Fixed #6 : ambiguity in mips_mem_free spec | m8pple | 2014-10-21 | 1 | -1/+1 |
| | |||||
* | Initial push. | m8pple | 2014-10-16 | 5 | -0/+560 |