Sponsored Content
Top Forums Programming Compilation problem with gfortran Post 302543069 by drl on Friday 29th of July 2011 10:22:49 AM
Old 07-29-2011
Hi.

How is my use of iargc in the example "f1" different from your use of iargc? ... cheers, drl
 

10 More Discussions You Might Find Interesting

1. Solaris

compilation problem

I am compiling a software named wine When i run make then at the end following error generated. DVAPI32_ -foversion.res version.rc ld.so.1: ../../tools/wrc/wrc: fatal: relocation error: file ../../tools/wrc/wrc: symbol wine_casemap_upper: referenced symbol not found *** Signal 9 make:... (0 Replies)
Discussion started by: mansoorulhaq
0 Replies

2. Programming

compilation problem

i have a class name 1.c in tht i am using function n wich has his body in 2.c and declaration in 2.h now how can i compile 1.c. ex; 1.c int main() { //some data n(10); //somedata } ***** 2.c int n(int k) { //some data } int main() { some data (2 Replies)
Discussion started by: phani_sree
2 Replies

3. Programming

Compilation problem on HP-UX

Hi, Environment : HP-UX avalon B.11.11 U 9000/800 3547052374 unlimited-user license aCC version :aCC: HP ANSI C++ B3910B A.03.37 I need to find a way out of this errors.can anyone help me . $ aCC db.cc -I$ORACLE_HOME/rdbms/public -I/disk1/oracle/product/10.2.0.2/* Error (future)... (1 Reply)
Discussion started by: varuntayur
1 Replies

4. AIX

Pro C Compilation problem

Hi, I have AIX 5.3 and my code is written in proc . i am getting following error during compilation Please help?////..... :-d: Compiling with RMS cc -w -q32 -qidirfirst -ISource/Header -I/usr/vacpp/include -q32 -DRMS -DDISEC -DDBG -DBIGENDIAN -DBIT32 -c -q32... (0 Replies)
Discussion started by: ajaysahoo
0 Replies

5. AIX

Compilation problem

hi, I first want to apologize for my poor english ! I'm a newbe on Unix system and I have to install NRPE on an AIX 5.3. I have downloaded the NRPE Source code and i need to compile them... the problem is, when I do a: ./configure --enable-command-args --disable-ssl it returns me :... (1 Reply)
Discussion started by: Cyr1us
1 Replies

6. Programming

C Compilation problem

Dear all I am new to C programming In response to the post cat get_time.c #include <stdlib.h> #include <sys/time.h> main() { struct timeval tv; struct timezone tz; struct tm *tm; gettimeofday(&tv, &tz); tm=localtime(&tv.tv_sec); printf("... (2 Replies)
Discussion started by: on9west
2 Replies

7. AIX

Problem in compilation.

Hi, I am executing the below mentioned code:- proc SQLCHECK=SEMANTICS iname=CDBInteractor.pc parse=none code=cpp cpp_suffix=cpp g++ -c main.cpp g++ -o pre_request_engine main.o -I/oracle/oracle/app/product/10g/precomp -L/oracle/oracle/app/product/10g/lib32 -lnsl -ldl And... (2 Replies)
Discussion started by: tushar_tus
2 Replies

8. Programming

gfortran compiling problem,calling too many arguments

Hello, My problem is with compiling a program modelling shallow water. In it there is a subroutine called stat with 9 parameters. In the main program it is called with 9 parameters also I'm running Ubuntu 11.04 with gfortran version 4.5. Thanks. ---------- Post updated at 11:57 PM... (0 Replies)
Discussion started by: b_franz
0 Replies

9. Programming

problem compiling with gfortran in two different debian releases

Hello, I hope this is the correct forum for this post. I have the following problem: A Fortran 77 program that has to deal with several large matrices (each approx. 5000 x 5000) and uses lapack and blas subroutines has been correctly compiled and executed using Debian Etch. When I tried... (1 Reply)
Discussion started by: currix
1 Replies

10. Programming

GFORTRAN library problem: libgFORTRAN.so.1 cannot open....

I've received some executable script for test, but executing this script continuously give me following message ./example: error while loading shared libraries: libgfortran.so.1: cannot open shared object file: No such file or directory Google search told me to do as following $... (1 Reply)
Discussion started by: exsonic
1 Replies
Xlate(5)							File Formats Manual							  Xlate(5)

NAME
Xlate, CreateXlate, AddXlateAddress, XlateInstTextStart, XlateInstTextSize, XlateLoadShift, XlateAddr - Atom routines used to determine the instrumented PC for selected instructions SYNOPSIS
The following interfaces are defined for use by Atom instrumentation routines: #include <cmplrs/atom.inst.h> XLATE *CreateXlate( Obj *obj, unsigned size ); void AddXlateAddress( XLATE *pxlt, Inst *inst ); The following interfaces are defined for use by Atom analysis routines: #include <cmplrs/atom.anal.h> unsigned long XlateNum( XLATE *pxlt ); unsigned long XlateInstTextStart( XLATE *pxlt ); unsigned long XlateInstTextSize( XLATE *pxlt ); long XlateLoadShift( XLATE *pxlt ); unsigned long XlateAddr( XLATE *pxlt, unsigned idx ); PARAMETERS
Pointer to an object within the application. Size of the address translation buffer (XLATE) to be created. Specify the size in terms of the number of instructions to be added to the buffer. If you do not know the number of instructions to be added, pass the special value XLATE_NOSIZE. Location to which CreateXlate returns a pointer to an address translation buffer (XLATE) or, for AddXlateAddress and the analysis routine functions, a pointer to an existing address translation buffer. Pointer to an instruction within the application. Inte- ger indicating the position of an instruction in the specified address translation buffer for which XlateAddr returns an instrumented run- time address. DESCRIPTION
Atom's Xlate routines allow you to determine the instrumented PC for selected instructions. You can use these functions to build a table that translates an instruction's PC in the instrumented application to its PC in the uninstrumented application. An Atom tool performs this translation by means of an address translation buffer (XLATE) created at instrumentation time and passed to analysis code at run time. You can use this buffer at analysis time to get the instrumented address for a selected set of instructions. An Atom tool's instrumentation routine creates and fills the address translation buffer by calling the CreateXlate and AddXlateAddress rou- tines, respectively. An address translation buffer can only hold instructions from a single object, the object identified by the obj parameter to the CreateXlate call. The AddXlateAddress routine adds the instruction indicated by the inst parameter to an existing address translation buffer. For an analysis routine to be able to translate its address at run time, you must add an instruction to an address translation buffer at instrumentation time. If the translation buffer was created with a fixed size and this instruction exceeds that size, the AddXlateAddress routine reports an error. You must add instructions to the buffer before you write the associated object. Only instructions from a single object may be added to a buffer. An Atom tool's instrumentation passes an address translation buffer to an analysis routine by using a parameter of type XLATE *, as indi- cated in the analysis routine's prototype definition in an AddCallProto call. For example: #include <cmplrs/atom.inst.h> void InstrumentInit(int iargc, char **iargv) { /* * Add the prototype for an analysis routine that accepts an * Xlate argument. */ AddCallProto("mycall(XLATE *)"); } Instrument(int iargc, char **iargv, Obj *obj) { Xlate * pxlate; Proc * p; /* * Create a new Xlate. */ pxlate = CreateXlate(obj, XLATE_NOSIZE); /* * Add the starting address of each procedure to the Xlate. */ for (p = GetFirstObjProc(obj); p; p = GetNextProc(p)) { AddXlateAddress(pxlate, GetFirstInst(GetFirstBlock(p))); } /* * Pass the Xlate to the analysis routines. */ AddCallObj(obj, ObjBefore, "mycall", pxlate); } Note It is illegal to pass an address translation buffer created for one object as a parameter to a call from another object. For this reason, it is normally inappropriate to pass address translation buffers as parameters to analysis routines inserted at a PlaceType of ProgramBe- fore and ProgramAfter. When the instrumentation routine specifies a formal parameter type of REGV (that is, register value) in an analysis routine's prototype definition, it can pass an instrumented version of a PC to the analysis routine by using the REG_IPC type. See atom_application_instrumen- tation(5) for further details. An Atom tool's analysis routine uses the following interfaces to access an address translation buffer that is passed to it: The XlateNum routine returns the number of addresses in the specified address translation buffer. The XlateInstTextStart routine returns the starting address of the text segment for the instrumented object corresponding to the specified address translation buffer. The XlateInstTextSize routine returns the size of the text segment. The XlateLoadShift routine returns the difference between the run-time addresses in the object corresponding to to the specified address translation buffer and the compile-time addresses. The XlateAddr routine returns the instrumented run-time address for the instruction in the specified position of the specified address translation buffer. Note that the run-time address for an instruction in a shared library is not necessarily the same as its compile-time address. The following example shows how an analysis routine retrieves information from an address translation buffer: #include <cmplrs/atom.anal.h> void mycall(XLATE *pxlate) { unsigned n; unsigned i; /* * Get the number of addresses in the Xlate. */ n = XlateNum(pxlate); /* * Print the instrumented address for the start of each procedure. */ printf("Instrumented procedure starting addresses "); for (i = 0; i < n; i++) printf("0x%lx0, XlateAddr(pxlate, i)); } RETURN VALUES
These routines return the values described in the preceding section. FILES
Header file containing external definitions of Atom routines SEE ALSO
Commands: atom(1) AtomTools: hiprof(5), pixie(5), third(5) Functions: atom_application_instrumentation(5), atom_application_navigation(5), atom_application_resolvers(5), atom_application_query(5), atom_description_file(5), atom_object_management(5), atom_instrumentation_routines(5), AnalHeapBase(5) Programmer's Guide Xlate(5)
All times are GMT -4. The time now is 11:53 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy