| United States-English |
|
|
|
![]() |
HP aC++ Version A.01.15 Release Notes: HP Series 9000 > Chapter 4 Problem Descriptions and Fixes and Known LimitationsKnown Problems |
|
Customers on support can use the product number to assist them in finding SSB and SRB reports for HP aC++. The product number you can search for is B3910BA. To verify the product number and version for your HP aC++ compiler, execute the following HP-UX commands:
To verify the product number and version for the linker:
To verify the product number and version for the shared library initializer:
Following are known problems and workarounds. As the ANSI C++ draft standard has evolved over time, the Standard C++ Library has not always kept up. Such is the case for the "times" function object in the functional header file. In the standard, "times" has been renamed to "multiplies." If you want to use "multiplies" in your code, to be compatible with the ANSI C++ draft standard, use a conditional compilation flag on the aCC command line. For example, for the following program, compile with the command line: aCC -D__HPACC_USING_MULTIPLIES_IN_FUNCTIONAL test.c
Depending on the existence of the conditional compilation flag, functional defines either "times", or "multiplies", not both. So, if you have old source that uses "times" in header functional and also new source that uses "multiplies", the sources cannot be mixed. Mixing the two sources would constitute a non-conforming program, and the old and new sources may or may not link. If your code uses the old name "times," and you want to continue to use the now non-standard "times" function object, you do not need to do anything to compile the old source. If you see a message like the following, you may be using a non-current version of the HP aC++ run-time support library.
For example, if you are a library distributor, you must ensure that your customers use the same or a newer version of the libCsup run-time library as you. If necessary, you should install the most current HP aC++ library support patch and distribute this patch to your customers.As of the date of these release notes, the most current library support patch number is: PHSS_15043 If you use explicit instantiation instead of closing a library, and you compile with the +inst_auto option, then unsatisfied symbols will be generated for inline template functions that are too large to inline. If you see the following error message, it means that CLOCKS_PER_SEC is not defined:
The workaround is to modify the /usr/include/sys/time.h file as follows:
The /usr/include/sys/time.h file contains a K & R style function declaration for which HP aC++ generates an error like the following:
To workaround, whenever time.h is included by a source program, you can define the __STDC__ macro on your command-line, as in the following example:
Or you can install the appropriate patch listed below:
HP aC++ generatres an error like the following stating that structs or any types cannot be declared extern.
The error is caused by a problem in the /usr/include/sys/time.h file. To workaround, you can change the line extern struct sigevent; in the time.h file to:
Or you can install the appropriate patch listed below:
To resolve a conflict between the exception struct in /usr/include/sys/math.h and the aC++ exception struct, the workaround is to modify the /usr/include/math.h file as follows:
Alternatively, you can install the PHCO_9261 patch. Compile-time warnings like the following should be ignored. They are caused by an incorrect prototype in the /usr/include/rpc/xdr.h file.
An application that ran on previous HP-UX 10.x releases (10.01, 10.10, or 10.20) will generally continue to run with the same behavior with this 10.20-based HP aC++ release provided that any dependent shared libraries are also present. An executable is a binary file that has been processed by the HP linker with ld or indirectly with the compiler, and can be run by the HP-UX loader(exec). The following items describe exceptions to binary compatibility between the previous 10.20 and current releases. These conditions can occur during your development process, but rarely affect deployed applications. Under the following conditions, when you compile your source code without any changes (to source code, options, or makefiles), you can create relocatable object files or executables that cannot be moved back to a previous 10.x system.
When you make changes to your source code, options, or makefiles to use new features of the current release, you can introduce the following area of binary incompatibility.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||