diff --git a/documentation/README.hpux b/documentation/README.hpux
index 85b2dee08..3b8ef8cd0 100644
--- a/documentation/README.hpux
+++ b/documentation/README.hpux
@@ -39,6 +39,11 @@ Tools needed
     configuration file ../configure/os/CONFIG_SITE.Common.hpux-parisc-gnu
     to make the EPICS builds use it.
 
+IMPORTANT NOTE: aCC is the standard C++ compiler for EPICS on HP-UX 11.
+Compiling Base with the GNU compiler set is experimental. Usually things
+will compile, but applications may experience problems. (See below.) For
+productional systems, using aCC is strictly recommended.
+
 
 Environment
 -----------
@@ -51,9 +56,9 @@ before starting to compile base.
 Building
 --------
 
-Should be quite normal. Edit the CONFIG_SITE files and "make". (Be sure
-that GNU make is in your path or call it explicitly as the standard make
-on HP is _not_ GNU.)
+Should be quite straightforward. Edit the CONFIG_SITE files and "make".
+(Be sure that GNU make is in your path or call it explicitly as the
+standard make on HP is _not_ GNU.)
 
 When compiling with aCC, you will see quite a few warning messages. Most
 of these warnings - if not all - will be in system header files. There
@@ -102,25 +107,27 @@ recompiling using the "chatr" (change attributes) command.
 Known Possible Problems
 -----------------------
 
- o There is a problem with some CA clients not detecting a network
-   connection going down. This only applies to clients that are trying
-   to write to the IOC at the moment the connection goes down. When the
-   IOC is up again, the client reconnect after a moment (~1 min.) - a
-   regular IOC reboot works. It's just in some cases that a client
-   (e.g. display manager) might not react as expected (e.g. turn
-   graphical elements white) while the connection is lost.
-
+ o Using the GNU compiler is experimental.
+   - CA clients compiled with the GNU compiler have some serious
+     problems related to the connection loss management of Channel
+     Access. This shows up as sudden messages "Unable to contact CA
+     repeater" and loss of the CA repeater connection. When the IOC gets
+     back after a reboot, the client program may never reconnect and has
+     to be restarted. I will be looking into this problem so that
+     hopefully it will go away in a future release. But: aCC is the main
+     platform, getting things to run under GNU is a low priority task
+     for me, so any help is appreciated very much.
+   - Caveat: To be compatible with HP-UX 10, GCC defaults to use the DCE
+     (user space) threads package. If you see messages like "errLogInit
+     failed" when running a Channel Access client, you are probably
+     linking against the old DCE threads library instead of libpthread.
+  
  o The 3.13 compatibility mode has passed some general testing for both
    native and GNU compilers with static and shared libraries and for
    statically and dynamically linked builds. Not every combination has
    been thoroughly tested. If the build system won't build your 3.13
    application successfully, contact me.
 
- o Caveat: To be compatible with HP-UX 10, GCC defaults to use the DCE
-   (user space) threads package. If you see messages like "errLogInit
-   failed" when running a Channel Access client, you are probably
-   linking against the old DCE threads library instead of libpthread.
-
 
 Please feel free to contact me if you encounter serious problems.