FWIW - the GNU qsort v routine which is part of standard C on Linux (glib 2.3.3) is probably about 10 times faster than this heapsort, except possibly for very special applications.
In other words you could replace all this with about 10 lines of C if you don't need portability. It looks like it was written to run under several compilers - so a rewrite may not work for you.
Whats the difference between 32bit and 64bit OS's or applications. I understand it a little but its just not clicking the way the teacher explained to me
thanks, any info would be much appreciated (1 Reply)
when using the command :
cat /proc/cpuinfo I get some basic info back on the cpu..
but it doesn't tell me if I am using a 64 or 32 bit processor ..
a) is this the right command to find this ?
b) if it is not what is ? and how do I get that information..
thanx moxxx68 (2 Replies)
Where can I get a list that maps the each Linux version to corresponding 32/64 bits model?
e.g.
OS -> Model (ILP32, LP64, ...)
RHLE3 -> ?
RHLE4 -> ?
RHLE5 -> ?
...
It would be better if there is such a list that contains most of current UNIX OS versions.
... (1 Reply)
i have solaris 10 x86 64bit installed on my pc (dell 3100). i then decided to move my hard drive to another pc (dell 4600). I noticed that each time i boot up, the OS show as 32 bit (instead of 64bit) and i can't even get past this stage to the login page.
when i moved it back to dell 3100 it... (13 Replies)
Not really a Unix question as such :o, but what advantages or disadvantages are there between using 32bit or 64bit applications on a T5220 running Solaris 10? What about mixing them e.g. 64 bit app using 32 bit libraries or vice versa? (1 Reply)
I have an application which builds and executes without error on a 32bit implementation of Linux. When I transferred the code to a new project on a 64bit implementation, the code will build without error, but the pthread functions, such as pthread_attr_setschedparam() return an 'Invalid Argument'... (3 Replies)
Hi Gurus,
I need to check whether the compiler installed in my system supports 64bit compilation.
Server - Sun fire v490
OS - Solaris 5.9
Processor - Sparcv9 (64bit)
Install Directory - /opt/SUNWSpro
Compiler Model - Sun Forte C Compiler.
My development team is claiming that there... (20 Replies)
Hi,
I have a C code which builds and works fine on 32bit linux machine.
Now i want to convert that code to build and run on 64 bit linux machine. I dont want to maintain two separate sources for 32 and 64 bit build. Same source should get build on 32 as well as 64 bit machine (when a... (2 Replies)
Hello, I am trying to use a worktool on SLES 10 (32-bit) and it is saying I do not have libcap.so.2:
error while loading shared libraries: libcap.so.2: cannot open shared object file: No such file or directory
Is there an easy way for me to install this library? A quick Google search... (4 Replies)
Discussion started by: bstring
4 Replies
LEARN ABOUT CENTOS
pmcpp
PMCPP(1) General Commands Manual PMCPP(1)NAME
pmcpp - simple preprocessor for the Performance Co-Pilot
SYNOPSIS
pmcpp [-D name[=value] ...] [infile]
DESCRIPTION
pmcpp provides a very simple pre-processor for manipulating Performance Metric Name Space (PMNS) files for the Performance Co-Pilot (PCP).
It is most commonly used internally to process the PMNS file(s) after pmLoadNameSpace(3) or pmLoadASCIINameSpace(3) is called.
Input lines are read from infile (or standard input if infile is not specified), processed and written to standard output.
All C-style comments of the form /* ... */ are stripped from the input stream.
There are no predefined macros for pmcpp although macros may be defined on the command line using the -D option, where name and value must
follow the same rules as described below for the #define directive.
pmcpp accepts the following directives in the input stream (like cpp(1)):
* #include "filename"
or
#include <filename>
In either case the directory search path for filename tries filename first, then the directory for the command line infile (if any),
followed by the $PCP_VAR_DIR/pmns directory. #include directives may be nested, up to a maximum depth of 5.
* #define name value
Defines a value for the macro name which must be a valid C-style name, so leading alphabetic or ``_'' followed by zero or more alphanu-
merics or ``_''. value is optional (and defaults to an empty value) but when present it may not contain white space and quoting or
escaping is not supported.
* #undef name
Removes the macro definition, if any, for name.
* #ifdef name
...
#endif
or
#ifndef name
...
#endif
The enclosing lines will be stripped or included, depending if the macro name is defined or not.
Macro substitution is achieved by breaking the input stream into words separated by white space or one of the characters ``.'' or ``:'' -
this matches the syntax of the PMNS, see pmns(5). Each word is checked and if it matches a macro name, the word is replaced by the macro
value, otherwise the word is unchanged.
There is generally one output line for each input line, although the line may be empty if the text has been stripped due to the handling of
comments or conditional directives. When there is a change in the input stream, an additional output line is generated of the form:
# line "name"
to indicate the following line of output corresponds to line number line of the input file name.
Important cpp(1) features that are not supported by pmcpp include:
* #if expr
...
#endif
* Nested use of #ifdef or #ifndef.
* #else within an #ifdef or #ifndef.
* Stripping C++ style comments, as in // comment
* Error recovery - the first error encountered by pmcpp will be fatal.
* cpp(1) command line options like -U , -P and -I.
PCP ENVIRONMENT
Environment variables with the prefix PCP_ are used to parameterize the file and directory names used by PCP. On each installation, the
file /etc/pcp.conf contains the local values for these variables. The $PCP_CONF variable may be used to specify an alternative configura-
tion file, as described in pcp.conf(5).
SEE ALSO cpp(1), pmLoadASCIINameSpace(3), pmLoadNameSpace(3), pmns(5), pcp.conf(5) and pcp.env(5).
Performance Co-PilotPMCPP(1)