The seL4 kernel itself does not need anything for running C++ support. However, a version of the C++ standard library would need to be ported / implemented to a particular seL4 environment. If you would like to compile C++ code that does not use the standard library then this relatively easy and there is a trivial example in sel4test (see https://github.com/seL4/sel4test/blob/master/apps/sel4test-tests/src/tests/domains.cxx and https://github.com/seL4/sel4test/blob/master/apps/sel4test-tests/Makefile)

I had some success with using my native gcc C++ libraries for compilation, although it was a little fiddly to make work. The idea there is that since the C++ standard libraries depend upon the syscalls and other symbols defined in the C library you can just link against your native C++ libraries, and rely on the ported C library (in our case muslc) to implement the syscalls and make everything work.
I am not promoting this as a good idea or a way to build a reliable system, but might give you a bit of insight into what is required for a proper C++ port.

Adrian

On 17/06/15 08:32, Yuxin Ren wrote: