File: pvm_archcode.3

package info (click to toggle)
pvm 3.4beta7-4
  • links: PTS
  • area: main
  • in suites: slink
  • size: 5,256 kB
  • ctags: 5,938
  • sloc: ansic: 66,147; makefile: 1,446; fortran: 631; sh: 424; csh: 70; asm: 37
file content (58 lines) | stat: -rw-r--r-- 1,475 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
.\" $Id: pvm_archcode.3,v 1.1 1996/09/23 22:01:01 pvmsrc Exp $
.TH ARCHCODE 3PVM "15 March, 1994" "" "PVM Version 3.4"
.SH NAME
pvm_archcode \- Returns the data representation code for a
PVM architecture name.

.SH SYNOPSIS
.nf
.ft B
C	int cod = pvm_archcode( char *arch )
.br

Fortran	call pvmfarchcode( arch, cod )
.fi

.SH PARAMETERS
.IP arch 0.8i
Character string containing the architecture name.
.br
.IP cod
Integer returning architecture code.
.SH DESCRIPTION
The routine
.I pvm_archcode
returns an integer given an architecture name.
The code returned identifies machines with compatible binary data formats.
For example, SUN4 and RS6K have the same code,
while ALPHA has a different one (because a few datatypes have different
sizes).
This lets you know when you can get away with using \fIPvmDataRaw\fR
instead of \fIPvmDataDefault\fR
encoding to pass messages between tasks on two machines.
.PP
Naturally,
you shouldn't assume the values returned by pvm_archcode are etched in stone;
the numbers have no intrinsic meaning except that
if two different arch names map to the same value then they're compatible.
.SH EXAMPLES
.nf
C:
	struct pvmhostinfo *hip;
	int i;

	pvm_config((int *)0, (int *)0, &hip);
	i = pvm_archcode(hip[0].hi_arch);
.sp
Fortran:
	CALL PVMFARCHCODE( 'RS6K', k )
.fi

.SH ERRORS
No error conditions are be returned by \fIpvm_archcode\fR.
.SH SEE ALSO
pvm_config(3PVM),
pvm_initsend(3PVM),
pvm_notify(3PVM),
pvm_tasks(3PVM),
pvm_tidtohost(3PVM)