omniORB2.gif (2079 bytes)

omniORB2 under Sun C++ 5

attlogo6876_dk.gif (2280 bytes)
sideHome.gif (2321 bytes) sideDownload.gif (2450 bytes) sideDocumentation.gif (2512 bytes) sideFAQ.gif (2344 bytes) sidePatch.gif (2543 bytes) sideSearch.gif (2403 bytes)
Sun C++ 4.2 is currently what we use to compile code to put into service.

We are putting Sun C++ 5.0 under testing. There were a number of problems with Sun C++ 5.0. These range from incorrect code to simply being unable to produce linkable object code. With the latest Sun C++ compiler patch (107311-06 of Sep 20), the compiler at least seems to produce correct code. *BUT* it still generates incorrect exception handling code when using just the -O2 flag or no optimisation at all. Strangely, "-O2 -g" produces correct code. At least it seems to work with simple tests. If your programs crash when there are concurrent activities, try recompile with -g only.

Another annoying feature of the compiler is that it has a habit of taking up all the CPU cycles and huge amount of memory (350M) doing who knows what. Sometimes compiling a moderate size omniORB2 stub could take 20 minutes or so on a 300MHz UltraSparc.
 

For comments, feedback, etc, please see the 'Keeping in touch' page.
Copyright 1999 - AT&T Laboratories Cambridge