Visit Our UNIX and Linux User Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #978
Difficulty: Easy
The Linux kernel development community uses Git to manage the kernel source code.
True or False?
Linux & Unix Commands - Search Man Pages

checkobj(1) [bsd man page]

CHECKOBJ(1)						      General Commands Manual						       CHECKOBJ(1)

NAME
checkobj - check an object file to see whether it can be executed SYNTAX
checkobj [ -s ] [ -f ] [ -40 ] [ file ... ] DESCRIPTION
Checkobj attempts to determine whether the named files are valid executable binary files. It checks for size restrictions, including those due to the granularity of memory management on the PDP11. It is especially useful for overlaid object files, where there are a number of constraints. If a file is too large or improperly laid out, checkobj attempts to point out format changes that would allow the program to run. OPTIONS
Several options control the checks: -s Check for the use of separate I/D. If the file is separate executable, an error is flagged, and an appropriate way to load for a nonseparate machine is suggested if possible. -f Check for the use of floating point arithmetic without inclusion of the floating-point interpreter. -40 Combine the -s and -f options, to check for suitability for an 11/40-class PDP11. BUGS
The test for floating point is simple-minded. It is based on the definition of ``fltused'' by the C compiler and ``fptrap'' in the float- ing-point simulator. This test does not work if the object has been stripped. DIAGNOSTICS
The exit status is 0 if all named files are runnable with the specified options, nonzero otherwise. AUTHOR
Mike Karels, University of California, Berkeley 3rd Berkeley Distribution CHECKOBJ(1)

Check Out this Related Man Page

FEGETENV(3)						   BSD Library Functions Manual 					       FEGETENV(3)

NAME
fegetenv, feholdexcept, fesetenv, feupdateenv -- functions providing access to the floating-point environment. SYNOPSIS
#include <fenv.h> #pragma STDC FENV_ACCESS ON int fegetenv(fenv_t *envp); int feholdexcept(fenvt_t *envp); int fesetenv(fenv_t *envp); int feupdateenv(fenv_t *envp); DESCRIPTION
These functions provide the means to manage the entire floating-point environment--including both status flags and control modes--as a single entity. The fegetenv() function attempts to store the current floating-point environment in the object pointed to by envp. It returns zero if the environment was successfully stored, and a nonzero value otherwise. The feholdexcept() function saves the current floating-point environment in the object pointed to by envp, clears the floating-point status flags, and then installs a "non-stop" mode, if available, under which no traps are taken for floating-point exceptions (as is the case in default IEEE-754 floating-point execution). It returns zero if and only if such a mode was successfully installed. The fesetenv() function attempts to establish the floating-point environment represented by the object pointed to by envp. This object shall have been set by a call to fegetenv() or feholdexcept(), or be equal to a floating-point environment macro defined in <fenv.h>. Note that this function merely installs the floating-point status flags represented by its argument, and does not raise the corresponding floating- point exceptions. It returns zero if and only if the environment pointed to by envp was successfully installed. The feupdateenv() function attempts to save the currently raised floating-point flags, install the floating-point environment represented by *envp, and then raise the floating-point exceptions corresponding to the saved flags. The object pointed to by envp shall have been set by a call to fegetenv() or feholdexcept(), or be equal to a floating-point environment macro defined in <fenv.h>. It returns zero if and only if all of the specified actions were successfully carried out. SEE ALSO
fenv(3), feclearexcept(3), fegetexceptflag(3), fegetround(3), feraiseexcept(3), fesetexceptflag(3), fesetround(3), feraiseexcept(3) STANDARDS
These functions conform to ISO/IEC 9899:TC3. BSD
May 9, 2011 BSD

Featured Tech Videos