What exactly are side-effects in #pragma no_side_effect?

Question

Which of the following qualify as side-effects for the purposes of #pragma [no_side_effect|http://docs.sun.com/app/docs/doc/819-5265/bjaby?a=view#bjacp]:
1. dynamically allocating/deallocating memory using malloc/free or operator new/delete
2. exiting the function by throwing a C++ exception
3. temporarily changing the disposition for a signal (e.g., ignoring or suspending a signal)
4. creating a thread and joining with it

Answer 1

Thanks for your answers! Just to make sure I understand correctly: accessing the local state of the caller through a parameter is not a side-effect. I.e., in the following snippet the function has_no_side_effects() has no side-effects:
int get (int *p) { return *p; }
void set (int *p, int x) { *p = x; }
void has_no_side_effects () {
    int x;
    int y;
    set (&x, 0);    // not a side-effect (x is local)
    y = get (&x);   // same
}But in the following, has_side_effects() does:
void has_side_effects () {
    static int x;
    static int y;
    set (&x, 0);    // side-effect: writing a "global"
    y = get (&x);   // side-effect: reading a "global"
}Also, reading global const data (i.e., what might be in ROM) is not a side-effect. Correct? E.g.,
static const int global[] = { 1, 2 };
void has_no_side_effects () {
    int x;
    int y;
    x = global [0];   // not a side-effect, global is in ROM
    y = global [1];   // same
}