Compaq: FreePort Express User's Guide Appendix A

User's Guide

Appendix A: fpx Command Messages

This appendix provides a list of all the fpx messages and suggested user actions, if any.

In the program output, either on a screen or in a log file, each message starts with either "fpx" or "fpxt." If a message starts with "fpx," it pertains to the overall process that drives the translation. If the message starts with "fpxt," it pertains to the phase of the translation during which fpx searches for and translates SPARC code in the user executable.

Unless you include the -v option in the command line, fpx displays error and fatal messages only.

Levels of severity

The fpx command prints messages while translating a program. The severity levels are as follows:

Info	Most messages are informational and require no user action.
Warning	The fpx command issues warning messages and continues translation if it encounters a condition that could render the executable invalid - it might not run predictably or it might not run at all. With one exception, all messages beginning with the word INTERNAL are warnings. Please file a bug report if you encounter an INTERNAL message.
Error	The fpx command issues messages indicating an error for reasons described in the message itself. The error may or may not be fatal.
Fatal	The fpx command issues a fatal message and aborts translation if the input image is unsupported. See What kinds of executables can be translated? in Chapter 1 for a description of the supported user executables for SunOS SPARC.

Messages and user actions

The error messages and suggested user actions are as follows:

Branch delay slot contains invalid instruction: Severity level: Warning; Explanation: The translator detected an instruction in the input executable that may not execute properly. The instruction is a branch, but the opcode in the delay slot for the branch is not valid (that is, it is itself a branch).; User action: Run the untranslated executable on SunOS SPARC to verify that it runs correctly.

Ending analysis pass 2 - beginning code generation & output: Severity level: Informational; User action: None required. Generated when you use the -v option to fpx.

Error opening filename as input.: Severity level: Fatal; Explanation: The fpx command encountered an error while opening the indicated file.; User action: Check to see that the file exists and that you have permission to open it and read it.

Error opening filename as output.: Severity level: Fatal; Explanation: The translator could not create or write to the indicated file.; User action: Check that you have permission to write to the directory that is to contain the file, or to overwrite a possible existing file of the same name. Also check to ensure that the file system containing the file is not full.

Error reading filename.: Severity level: Fatal; Explanation: The fpx command encountered an error while reading the indicated file.; User action: Check to see that you have permission to read the file, and that it is in the format that fpx expects. See if the error-logging facility is recording errors for the device that contains the file.

Error writing file filename.: Severity level: Fatal; Explanation: The translator could not create the indicated file.; User action: Check that you have permission to write to the file. Also check to ensure that the file system containing the file is not full.

HIF entry: entry: Severity level: Informational; Explanation: This informational message appears if the verbose level (set with the -v option) is greater than 1. There is one line for each entry in the .hif file.; User action: None required.

Input file filename has currently unsupported magic number: octalinteger (octal).: Severity level: Fatal; Explanation: The indicated executable is an a.out file but does not have an a.out magic number that fpx recognizes.; User action: If possible, relink the executable on SunOS to one of the supported formats.

INTERNAL CONSISTENCY ERROR: An instance of a filename was not empty when deleted.: Severity level: Warning; Explanation: All errors beginning with the word INTERNAL are warnings. The translated executable is probably not valid.; User action: File a bug report. As a workaround, try translating with different command line options, or try not using a .hif file.

INTERNAL CONSISTENCY ERROR: Attempt to remove data from an empty instance of a filename.: Severity level: Warning; Explanation: All errors beginning with the word INTERNAL are warnings. The translated executable is probably not valid.; User action: File a bug report. As a workaround, try translating with different command line options, or try not using a .hif file.

INTERNAL CONSISTENCY ERROR: Attempt to split non-real-code basic block: Severity level: Warning; Explanation: All errors beginning with the word INTERNAL are warnings. The translated executable is probably not valid.; User action: File a bug report. As a workaround, try translating with different command line options, or try not using a .hif file.

INTERNAL CONSISTENCY ERROR: Branch target hexinteger is the middle of an instruction or call mask.: Severity level: Warning; Explanation: All errors beginning with the word INTERNAL are warnings. The translated executable is probably not valid.; User action: File a bug report. As a workaround, try translating with different command line options, or try not using a .hif file.

INTERNAL CONSISTENCY ERROR: Expected bb type filename, found type filename ; pgm location=integer.: Severity level: Warning; Explanation: All errors beginning with the word INTERNAL are warnings. The translated executable is probably not valid.; User action: File a bug report. As a workaround, try translating with different command line options, or try not using a .hif file.

INTERNAL CONSISTENCY ERROR: Insert called with NULL pointer!: Severity level: Warning; Explanation: All errors beginning with the word INTERNAL are warnings. The translated executable is probably not valid.; User action: File a bug report. As a workaround, try translating with different command line options, or try not using a .hif file.

INTERNAL CONSISTENCY ERROR: no memory: Severity level: Warning; Explanation: All errors beginning with the word INTERNAL are warnings. The translated executable is probably not valid.; User action: File a bug report. As a workaround, try translating with different command line options, or try not using a .hif file.

INTERNAL CONSISTENCY ERROR: Remove called with NULL pointer!: Severity level: Warning; Explanation: All errors beginning with the word INTERNAL are warnings. The translated executable is probably not valid.; User action: File a bug report. As a workaround, try translating with different command line options, or try not using a .hif file.

INTERNAL CONSISTENCY ERROR: Unexpected annotation detected; program location=integer.: Severity level: Warning; Explanation: All errors beginning with the word INTERNAL are warnings. The translated executable is probably not valid.; User action: File a bug report. As a workaround, try translating with different command line options, or try not using a .hif file.

INTERNAL CONSISTENCY ERROR: VA=hexinteger referenced but not in the image; pgm location= integer.: Severity level: Warning; Explanation: All errors beginning with the word INTERNAL are warnings. The translated executable is probably not valid.; User action: File a bug report. As a workaround, try translating with different command line options, or try not using a .hif file.

INTERNAL ERROR: filename: Severity level: Warning; Explanation: All errors beginning with the word INTERNAL are warnings. The translated executable is probably not valid. See associated messages for further explanation.; User action: File a bug report. As a workaround, try translating with different command line options, or try not using a .hif file.

INTERNAL ERROR: Action to be performed is not correctly specified: Severity level: Warning; Explanation: All errors beginning with the word INTERNAL are warnings. The translated executable is probably not valid.; User action: File a bug report. As a workaround, try translating with different command line options, or try not using a .hif file.

INTERNAL ERROR: Could not find map entry for domain # integer address hexinteger.: Severity level: Warning; Explanation: All errors beginning with the word INTERNAL are warnings. The translated executable is probably not valid.; User action: File a bug report. As a workaround, try translating with different command line options, or try not using a .hif file.

INTERNAL ERROR: Could not find successor number integer for Bb: Severity level: Warning; Explanation: All errors beginning with the word INTERNAL are warnings. The translated executable is probably not valid.; User action: File a bug report. As a workaround, try translating with different command line options, or try not using a .hif file.

INTERNAL ERROR: Element removed from bag while iterator(s) outstanding: Severity level: Warning; Explanation: All errors beginning with the word INTERNAL are warnings. The translated executable is probably not valid.; User action: File a bug report. As a workaround, try translating with different command line options, or try not using a .hif file.

INTERNAL ERROR: Illegal action found: Severity level: Warning; Explanation: All errors beginning with the word INTERNAL are warnings. The translated executable is probably not valid.; User action: File a bug report. As a workaround, try translating with different command line options, or try not using a .hif file.

INTERNAL ERROR: Internal inconsistency detected during code generation: Severity level: Warning; Explanation: All errors beginning with the word INTERNAL are warnings. The translated executable is probably not valid.; User action: File a bug report. As a workaround, try translating with different command line options, or try not using a .hif file.

INTERNAL ERROR: Internal inconsistency detected in filename: Severity level: Warning; Explanation: All errors beginning with the word INTERNAL are warnings. The translated executable is probably not valid.; User action: File a bug report. As a workaround, try translating with different command line options, or try not using a .hif file.

INTERNAL ERROR: Map error # integer detected.: Severity level: Warning; Explanation: All errors beginning with the word INTERNAL are warnings. The translated executable is probably not valid.; User action: File a bug report. As a workaround, try translating with different command line options, or try not using a .hif file.

INTERNAL ERROR: fpx has encountered a fatal exception (integer,nnnnnnnn) at nnnnnnnn: Severity level: Fatal; Explanation: The translated executable is probably not valid.; User action: File a bug report. As a workaround, try translating with different command line options, or try not using a .hif file.

INTERNAL ERROR: No more virtual memory to create data structures: Severity level: Warning; Explanation: All errors beginning with the word INTERNAL are warnings. The translated executable is probably not valid.; User action: File a bug report. As a workaround, try translating with different command line options, or try not using a .hif file.

INTERNAL ERROR: Tried to get another Bb successor after end of list: Severity level: Warning; Explanation: All errors beginning with the word INTERNAL are warnings. The translated executable is probably not valid.; User action: File a bug report. As a workaround, try translating with different command line options, or try not using a .hif file.

INTERNAL ERRORS: File a bug report: Severity level: Warning; Explanation: All errors beginning with the word INTERNAL are warnings. The translated executable is probably not valid.; User action: File a bug report.

Interpreter will be called if this code is reached at execution time: Severity level: Informational; Explanation: This message indicates that the interpreter will be required at run time.; User action: It may be possible to improve performance in the executable. Set the FPXR_GENERATE_FEEDBACK environment variable at run time. If a .hif file is created or extended at run time, retranslate the executable with the .hif file.

Message code xxx not found.: Severity level: Fatal; User action: File a bug report.

More than n type HIF entries - ignoring lowest frequency ones: Severity level: Informational; Explanation: This message indicates that the SunOS program has a computed branch or call instruction at the indi cated address, and that at run time, fpxr detected more than n possible targets for the transfer of control. This number exceeds the translator's built-in limit for the number of targets allowed, so only the highest frequency targets are optimized.; User action: If this message appears, subsequent runs with feedback may append data to the .hif file, which cannot be used by fpx during retranslation, and you may want to stop the feedback/retranslate cycle.

More than 1 instance of local symbol xxx (used in .hif file) found in symbol table: Severity level: Warning; Explanation: The program has multiple instances of the indicated symbol in the symbol table and all of them are local symbols. fpx cannot differentiate among them, and the entry in the .hif file is ignored.; User action: None required.

No text for message type filename: Severity level: Fatal; User action: File a bug report.

No usable entries found in HIF file filename: Severity level: Informational; Explanation: The fpx command read a feedback file for information to enhance the translation, but found no usable entries in it.; User action: If the indicated .hif file was generated entirely by fpxr, file a bug report. If you hand-edited the .hif file, correct its syntax. See Writing a feedback file in Chapter 4, Enhancing performance.

Processing feedback from file filename: Severity level: Informational; User action: None required.

Reading file filename.: Severity level: Informational; User action: None required.

Redundant instruction deleted: Severity level: Informational; Explanation: The input executable has a redundant instruction at the indicated address. This is informational only, but indicates a place at which performance on SunOS may be degraded. fpx deletes the redundant instruction from the translated executable.; User action: None required.

Stack not longword aligned; change=0xnnnnnnnn: Severity level: Warning; Explanation: This indicates a potentially severe problem with the stack in input executable. The stack pointer must always be a multiple of 8.; User action: Run the untranslated executable on SunOS SPARC to verify that it runs correctly.

Stack pointer adjustments don't match on all incoming paths.: Severity level: Informational; Explanation: There are multiple ways to reach the code at the indicated address, and the stack depth is different along different paths. This indicates a potential problem in the original SunOS program.; User action: Run the untranslated executable on SunOS SPARC to verify that it runs correctly.

Starting analysis pass 1: Severity level: Informational; User action: None required. Generated when you use the -v option to fpx.

Starting analysis pass 2: Severity level: Informational; User action: None required. Generated when you use the -v option to fpx.

Symbol xxx (used in .hif file) not found in symbol table: Severity level: Warning; Explanation: The indicated symbol name was used in the .hif file, but that symbol does not appear in the symbol table for the program.; User action: Correct the .hif file.

Syntax error in file filename.hif: column n in record m: Severity level: Warning; Explanation: Syntax error in the feedback file.; User action: If the indicated .hif file was generated entirely by fpxr, file a bug report. If you hand-edited the .hif file, correct its syntax. See Writing a feedback file in Chapter 4, Enhancing performance.

Syntax error in file filename.hif: undefined symbol xxx.: Severity level: Warning; Explanation: Syntax error in the feedback file.; User action: If the indicated .hif file was generated entirely by fpxr, file a bug report. If you hand-edited the .hif file, correct its syntax. See Writing a feedback file in Chapter 4, Enhancing performance.

Syntax error in file filename.hif: unknown value type n: Severity level: Warning; Explanation: Syntax error in the feedback file.; User action: If the indicated .hif file was generated entirely by fpxr, file a bug report. If you hand-edited the .hif file, correct its syntax. See Writing a feedback file in Chapter 4, Enhancing performance.

Transfer of control into data found at pc = 0xnnnnnn: Severity level: Informational; Explanation: The translated executable requires the interpreter at run time if control transfers to the indicated address.; User action: If the interpreter is called at run time, it may be possible to improve performance in the executable. Set the FPXR_GENERATE_FEEDBACK environment variable at run time. If a .hif file is created or extended at run time, retranslate the executable with the .hif file. See Writing a feedback file in Chapter 4, Enhancing performance.

Translation completed successfully: Severity level: Informational; User action: None required.

Translation of executables is not supported: file filename: Severity level: Fatal; Explanation: The indicated file contains no section headers, and is not in a format that fpx can translate.; User action: Relink the executable on SunOS to create a standard ZMAGIC (or OMAGIC or NMAGIC) file.

Translation unsuccessful -- no output image created: Severity level: Fatal; Explanation: The fpx command was unable to create an executable from the input file.; User action: See other messages created during translation. Verify that the input executable is eligible for translation. See What kinds of executables can be translated? in Chapter 1, Introducing FreePort Express.

Translation was impossible: Severity level: Fatal; Explanation: The fpx command was unable to create an executable from the input file.; User action: See other messages created during translation. Verify that the input executable is eligible for translation. See What kinds of executables can be translated? in Chapter 1, Introducing FreePort Express.

Unknown command line option option: Severity level: Fatal; Explanation: The indicated option is not a valid fpx option.

If you have questions about FreePort Express, send email to fpx-info@scrugs.lkg.dec.com.

Click to send feedback