X-Git-Url: http://git.chise.org/gitweb/?a=blobdiff_plain;f=src%2Fs%2Faix4.h;h=56bd1a1128ee56b9e6658bd48745dab8fed7c1c1;hb=27ea365b3903728593fb2726e9336c1b49eb9f4f;hp=fe19cda8737ec46dab08f9aaf85b42196d40a3e4;hpb=b24a82be4ed4916738cbed097d8dfc96ec312435;p=chise%2Fxemacs-chise.git-

diff --git a/src/s/aix4.h b/src/s/aix4.h
index fe19cda..56bd1a1 100644
--- a/src/s/aix4.h
+++ b/src/s/aix4.h
@@ -17,14 +17,19 @@ struct sockaddr_dl;
 
 #ifdef __xlC__			/* "eXceLlent C compiler" ?! */
 #if __xlC__ >= 1200
-/* IBM's C compiler miscompiles bytecount_to_charcount at high levels
-   of optimization.  From IBM's docs:
+/* IBM's C compiler option `-O3' is too aggressive.
+   We recommend instead the combination `-O3 -qstrict', which seems safe.
 
-   -qstrict turns off the following optimizations:
+   cc -O3 miscompiles at least two functions.  From IBM's docs:
 
-   Performing code motion and scheduling on computations such as loads
-   and floating-point computations that may trigger an exception. */
+   IBM> -qstrict turns off the following optimizations:
+
+   IBM> Performing code motion and scheduling on computations such as loads
+   IBM> and floating-point computations that may trigger an exception.
+
+   Nevertheless, we try to work with these compiler options. */
 #pragma option_override (bytecount_to_charcount, "opt(strict,yes)")
+#pragma option_override (Fexpand_file_name, "opt(strict,yes)")
 #endif /* recent IBM C compiler */
 #endif /* IBM's C compiler */