aboutsummaryrefslogtreecommitdiff
path: root/qtmips_machine/qtmipsexception.h
blob: 41caa8784cc517aba6e401e72bd8f935b9a16c8c (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
#ifndef QTMIPSEXCEPTION_H
#define QTMIPSEXCEPTION_H

#include <exception>
#include <qstring.h>

namespace machine {

// Base exception for all machine ones
class QtMipsException : public std::exception {
public:
    QtMipsException(QString reason, QString ext, QString file, int line);
    const char *what() const throw();
    QString msg(bool pos) const;
protected:
    QString name, reason, ext, file;
    int line;
};

/* This is list of all QtMips specific exceptions
 *
 * Input:
 *  Exception durring input loading
 * Runtime:
 *  Exceptions caused by machine invalid input or unsupported action
 * UnsupportedInstruction:
 *  Decoded instruction is not supported.
 *  This can be cause by really using some unimplemented instruction or because of problems in instruction decode.
 * UnsupportedAluOperation:
 *  Decoded ALU operation is not supported
 *  This is basically same exception as QtMipsExceptionUnsupportedInstruction but it is emmited from ALU when executed and not before that.
 * Overflow:
 *  Integer operation resulted to overflow (or underflow as we are working with unsigned values)
 *  This is for sure caused by program it self.
 * UnalignedJump:
 *  Instruction is jumping to unaligned address (ADDR % 4 != 0)
 *  This can be caused by bug or by user program as it can be jumping relative to register
 *  This shouldn't be happening with non-register jumps as those should be verified by compiler
 * UnknownMemoryControl:
 *  Used unknown MemoryAccess control value (write_ctl or read_ctl)
 *  This can be raised by invalid instruction but in such case we shoul raise UnknownInstruction instead
 *  So this should signal just some QtMips bug.
 * OutOfMemoryAccess:
 *  Trying to access address outside of the memory
 *  As we are simulating whole 32bit memory address space then this is most probably QtMips bug if raised not program.
 * Sanity:
 *  This is sanity check exception
 */
#define QTMIPS_EXCEPTIONS \
    EXCEPTION(Input,) \
    EXCEPTION(Runtime,) \
    EXCEPTION(UnsupportedInstruction, Runtime) \
    EXCEPTION(UnsupportedAluOperation, Runtime) \
    EXCEPTION(Overflow, Runtime) \
    EXCEPTION(UnalignedJump, Runtime) \
    EXCEPTION(UnknownMemoryControl, Runtime) \
    EXCEPTION(OutOfMemoryAccess, Runtime) \
    EXCEPTION(Sanity,)

#define EXCEPTION(NAME, PARENT) \
    class QtMipsException##NAME : public QtMipsException##PARENT { \
    public: \
        QtMipsException##NAME(QString reason, QString ext, QString file, int line); \
    };
QTMIPS_EXCEPTIONS
#undef EXCEPTION


// This is helper macro for throwing QtMips exceptions
#define QTMIPS_EXCEPTION(TYPE, REASON, EXT) (machine::QtMipsException##TYPE (QString(REASON), QString(EXT), QString(__FILE__), __LINE__))

// Sanity comparison potentially throwing QtMipsExceptionSanity
#define SANITY_ASSERT(COND, MSG) do { if (!(COND)) throw QTMIPS_EXCEPTION(Sanity, "Sanity check failed (" #COND ")", MSG); } while (false)

}

#endif // QTMIPSEXCEPTION_H