Release notes for OpenCL 0.7.1

GCC3 snapshot 20010327 (and possibly others) will miscompile SAFER-SK and SHARK
with optimizations. If you get an error stating that
SecureAllcator<byte>::unlock has multiple definitions, remove safer_sk.o and
shark.o and rebuild them without any -O flags (just edit Config and rerun
make). This bug may show up in some other form with different source files; the
rememdy will probably be the same in all cases.

Both egcs 1.1.2 and many versions of gcc will produce a large number of
pointless warning messages (mostly related to the use of 64 bit constants
without the LL suffix, which is legal by C99, plus a bunch of things which are
totally useless). In any case, don't be concerned about it. Redirecting stderr
to /dev/null might be a wise idea. Unfortunately, some of these warnings occur
in the template code, so you'll see them if you compile code using OpenCL.
There really isn't much I can do about this; the only thing I can recommend is
use the latest gcc snapshots - gcc3 does not print these spurious warnings.

Patches have been released for MIPSPro C++, Compaq C++, and PGI C++. Remember
to apply them if appropriate.

PGI C++ has some build problems, which I have been unable to get around. A
build _is_ possible, but it took my some hours to do, and I only got it to
build twice out of over 15 trys. Most of the time the prelinker dies, saying
there is a corrupted template instantiation file. If someone can figure this
one out and get back to me, I'd appreciate it.

