🚀 go-pugleaf

This code:

#include <stdlib.h>

class foo {
private:
  int x;
public:
  foo() {};
  int check(int i);
  volatile void exit_handler() {exit(-1);}
};

int foo::check(int i) {
  if (i > 0)
    {exit_handler();}
  else
    {return 0;}
}

volatile void foo1() {exit(1);}

int foo2 (int argc) {
  if (argc > 2)
    {foo1();}
  else
    {return 0;}
}


produces the following warning message when compiled with 
"gcc -c -Wall foo.C":

	warning: control reaches end of non-void function

Note that this only occurs with the member function version of this
example. The function version, included above, doesn't produce a
warning message.

This is no doubt the result of some compiler magic going on behind the
scenes, but here is my question:

Shouldn't the declaration of the member function as volatile void
prevent such a warning message from occurring?

Volatile is supposed to be used when the function might never return,
so why doesn't the compiler turn off the warning message in this case?