pvm-3.4.5-165.1.x86_64 RPM
Distribution:
Version: 3.4.5
Release: 165.1
Build date: Sat Feb 19 03:59:55 2011
Build host: build22
Size: 1429753
Source RPM:
Packager: http://bugs.opensuse.org
Summary: Parallel Virtual Machine
PVM is a software system that enables a collection of heterogeneous
computers to be used as a coherent and flexible concurrent
computational resource.
The individual computers may be shared- or local-memory
multiprocessors, vector supercomputers, specialized graphics engines,
or scalar workstations, that may be interconnected by a variety of
networks, such as ethernet, FDDI.
User programs written in C, C++ or
Fortran access PVM through library routines.
After installation you find in /usr/share/doc/packages/pvm/ the
documentation as PostScript file pvm-book.ps.
Furthermore some
examples are packed together in two tar archives.
Those archives
should be extracted into your HOME directory which leads to
~/pvm3/examples/ or ~/pvm3/gexamples/ in your HOME directory.
`aimk all' (see manual page aimk(1)) e.g. in ~/pvm3/examples/ compiles
the examples for the PVM system.
The PVM web home page is at http://www.epm.ornl.gov/pvm/pvm_home.html .
J. J. Dongarra
&pvm@msr.epm.ornl.gov&
G. E. Fagg
&pvm@msr.epm.ornl.gov&
G. A. Geist
&pvm@msr.epm.ornl.gov&
J. A. Kohl
&pvm@msr.epm.ornl.gov&
R. J. Manchek
&pvm@msr.epm.ornl.gov&
&pvm@msr.epm.ornl.gov&
P. M. Papadopoulos &pvm@msr.epm.ornl.gov&
S. L. Scott
&pvm@msr.epm.ornl.gov&
V. S. Sunderam
&pvm@msr.epm.ornl.gov&
&= 3.0.4-1
LGPLv2.1+ ; MIT
* Mon Mar 01 2010 andrea@opensuse.org
- %%run_ldconfig is deprecated changed with /sbin/ldconfig
- make a valid PVM_ROOT symlinking missing files
- removed %%changelog, we have .changes file now
* Sat Nov 11 2006 mrueckert@suse.de
- dont install man pages with executable flag
* Thu Nov 09 2006 mrueckert@suse.de
- build with '-fPIC -DPIC' (#218356)
* Mon Apr 10 2006 mrueckert@suse.de
- build with &-fno-strict-aliasing&
* Wed Mar 22 2006 mrueckert@suse.de
- added pvm-3.4.5_missing_format_param.patch
o fixes missing parameter for printf expression. (#133904)
o use vsnprintf instead of vsprintf
* Wed Jan 25 2006 mls@suse.de
- converted neededforbuild to BuildRequires
* Mon Jan 23 2006 mrueckert@suse.de
- fixed the most urgent compiler warnings
* Mon Dec 19 2005 ro@suse.de
- remove unpackaged symlinks
* Tue Nov 15 2005 uli@suse.de
- fixed to build on ARM
* Thu Jun 30 2005 mrueckert@suse.de
- use RPM_OPT_FLAGS
/usr/bin/pvm
/usr/bin/pvm_gstat
/usr/bin/pvmd
/usr/bin/pvmgroups
/usr/bin/pvmgs
/usr/bin/tracer
/usr/bin/trcsort
/usr/lib/pvm3
/usr/lib/pvm3/bin
/usr/lib/pvm3/bin/LINUX64
/usr/lib/pvm3/bin/LINUX64/pvm_gstat
/usr/lib/pvm3/bin/LINUX64/pvmgroups
/usr/lib/pvm3/bin/LINUX64/pvmgs
/usr/lib/pvm3/bin/LINUX64/tracer
/usr/lib/pvm3/bin/LINUX64/trcsort
/usr/lib/pvm3/lib
/usr/lib/pvm3/lib/LINUX64
/usr/lib/pvm3/lib/LINUX64/libpvm3.so.3
/usr/lib/pvm3/lib/LINUX64/libpvm3.so.3.4
/usr/lib/pvm3/lib/LINUX64/pvm
/usr/lib/pvm3/lib/LINUX64/pvmd3
/usr/lib/pvm3/lib/LINUX64/pvmgs
/usr/lib/pvm3/lib/pvmd
/usr/lib/pvm3/lib/pvmgetarch
/usr/lib/pvm3/lib/pvmtmparch
/usr/lib64/libpvm3.so.3
/usr/lib64/libpvm3.so.3.4
/usr/share/doc/packages/pvm
/usr/share/doc/packages/pvm/examples
/usr/share/doc/packages/pvm/examples/AIX4SP2
/usr/share/doc/packages/pvm/examples/AIX4SP2/Makefile
/usr/share/doc/packages/pvm/examples/Makefile.aimk
/usr/share/doc/packages/pvm/examples/Makefile.mak
/usr/share/doc/packages/pvm/examples/OS2
/usr/share/doc/packages/pvm/examples/OS2/Makefile
/usr/share/doc/packages/pvm/examples/PGON
/usr/share/doc/packages/pvm/examples/PGON/Makefile
/usr/share/doc/packages/pvm/examples/Readme
/usr/share/doc/packages/pvm/examples/SP2MPI
/usr/share/doc/packages/pvm/examples/SP2MPI/Makefile
/usr/share/doc/packages/pvm/examples/bwtest.c
/usr/share/doc/packages/pvm/examples/cygwin.mak
/usr/share/doc/packages/pvm/examples/gexample.c
/usr/share/doc/packages/pvm/examples/gexample.f
/usr/share/doc/packages/pvm/examples/gmbi.c
/usr/share/doc/packages/pvm/examples/hello.c
/usr/share/doc/packages/pvm/examples/hello_other.c
/usr/share/doc/packages/pvm/examples/hitc.f
/usr/share/doc/packages/pvm/examples/hitc_slave.f
/usr/share/doc/packages/pvm/examples/inherit1.c
/usr/share/doc/packages/pvm/examples/inherit2.c
/usr/share/doc/packages/pvm/examples/inherit3.c
/usr/share/doc/packages/pvm/examples/inherita.c
/usr/share/doc/packages/pvm/examples/inheritb.c
/usr/share/doc/packages/pvm/examples/lmbi.c
/usr/share/doc/packages/pvm/examples/master1.c
/usr/share/doc/packages/pvm/examples/master1.f
/usr/share/doc/packages/pvm/examples/mbox.c
/usr/share/doc/packages/pvm/examples/mhf_server.c
/usr/share/doc/packages/pvm/examples/mhf_tickle.c
/usr/share/doc/packages/pvm/examples/ptest.c
/usr/share/doc/packages/pvm/examples/rme.c
/usr/share/doc/packages/pvm/examples/slave1.c
/usr/share/doc/packages/pvm/examples/slave1.f
/usr/share/doc/packages/pvm/examples/spmd.c
/usr/share/doc/packages/pvm/examples/spmd.f
/usr/share/doc/packages/pvm/examples/starter.c
/usr/share/doc/packages/pvm/examples/task0.c
/usr/share/doc/packages/pvm/examples/task1.c
/usr/share/doc/packages/pvm/examples/task_end.c
/usr/share/doc/packages/pvm/examples/taskf.c
/usr/share/doc/packages/pvm/examples/timing.c
/usr/share/doc/packages/pvm/examples/timing_slave.c
/usr/share/doc/packages/pvm/gexamples
/usr/share/doc/packages/pvm/gexamples/CSPP
/usr/share/doc/packages/pvm/gexamples/CSPP/Makefile
/usr/share/doc/packages/pvm/gexamples/Makefile
/usr/share/doc/packages/pvm/gexamples/Makefile.aimk
/usr/share/doc/packages/pvm/gexamples/Makefile.mak
/usr/share/doc/packages/pvm/gexamples/OS2
/usr/share/doc/packages/pvm/gexamples/OS2/Makefile
/usr/share/doc/packages/pvm/gexamples/PGON
/usr/share/doc/packages/pvm/gexamples/PGON/Makefile
/usr/share/doc/packages/pvm/gexamples/Readme
/usr/share/doc/packages/pvm/gexamples/frsg.f
/usr/share/doc/packages/pvm/gexamples/ge.c
/usr/share/doc/packages/pvm/gexamples/gexamp.c
/usr/share/doc/packages/pvm/gexamples/gs.c
/usr/share/doc/packages/pvm/gexamples/joinleave.c
/usr/share/doc/packages/pvm/gexamples/thb.c
/usr/share/doc/packages/pvm/gexamples/tjf.c
/usr/share/doc/packages/pvm/gexamples/tjl.c
/usr/share/doc/packages/pvm/gexamples/tnb.c
/usr/share/doc/packages/pvm/gexamples/trsg.c
/usr/share/doc/packages/pvm/gexamples/tst.c
/usr/share/doc/packages/pvm/hoster
/usr/share/doc/packages/pvm/hoster/Makefile.aimk
/usr/share/doc/packages/pvm/hoster/Makefile.mak
/usr/share/doc/packages/pvm/hoster/OS2
/usr/share/doc/packages/pvm/hoster/OS2/Makefile
/usr/share/doc/packages/pvm/hoster/Readme
/usr/share/doc/packages/pvm/hoster/hoster.c
/usr/share/doc/packages/pvm/hoster/pvm_getminfo.3
/usr/share/doc/packages/pvm/hoster/pvm_setminfo.3
/usr/share/doc/packages/pvm/hoster/pvmfgetminfo.3
/usr/share/doc/packages/pvm/hoster/pvmfsetminfo.3
/usr/share/doc/packages/pvm/hoster/pvmwinrexec.c
/usr/share/doc/packages/pvm/hoster/pvmwinrsh.c
/usr/share/doc/packages/pvm/misc
/usr/share/doc/packages/pvm/misc/Readme
/usr/share/doc/packages/pvm/misc/group-hack-337
/usr/share/doc/packages/pvm/misc/pvm_fork.c
/usr/share/doc/packages/pvm/misc/xhoster
/usr/share/doc/packages/pvm/misc/xhoster/Imakefile
/usr/share/doc/packages/pvm/misc/xhoster/Makefile
/usr/share/doc/packages/pvm/misc/xhoster/README
/usr/share/doc/packages/pvm/misc/xhoster/hostc.c
/usr/share/doc/packages/pvm/misc/xhoster/hostc.h
/usr/share/doc/packages/pvm/misc/xhoster/myalloc.h
/usr/share/doc/packages/pvm/misc/xhoster/xhoster.c
/usr/share/doc/packages/pvm/tasker
/usr/share/doc/packages/pvm/tasker/Makefile.aimk
/usr/share/doc/packages/pvm/tasker/tasker.c
/usr/share/doc/packages/pvm/xep
/usr/share/doc/packages/pvm/xep/Makefile.aimk
/usr/share/doc/packages/pvm/xep/PGON
/usr/share/doc/packages/pvm/xep/PGON/Makefile
/usr/share/doc/packages/pvm/xep/PMAX
/usr/share/doc/packages/pvm/xep/PMAX/Makefile
/usr/share/doc/packages/pvm/xep/TrueColorFix
/usr/share/doc/packages/pvm/xep/bars.xbm
/usr/share/doc/packages/pvm/xep/calc.c
/usr/share/doc/packages/pvm/xep/color.xbm
/usr/share/doc/packages/pvm/xep/hostc.c
/usr/share/doc/packages/pvm/xep/hostc.h
/usr/share/doc/packages/pvm/xep/imp.c
/usr/share/doc/packages/pvm/xep/imp.h
/usr/share/doc/packages/pvm/xep/into.xbm
/usr/share/doc/packages/pvm/xep/mmain.c
/usr/share/doc/packages/pvm/xep/mtile.c
/usr/share/doc/packages/pvm/xep/myalloc.h
/usr/share/doc/packages/pvm/xep/neww.xbm
/usr/share/doc/packages/pvm/xep/outof.xbm
/usr/share/doc/packages/pvm/xep/quit.xbm
/usr/share/doc/packages/pvm/xep/redo.xbm
/usr/share/doc/packages/pvm/xep/reset.xbm
/usr/share/doc/packages/pvm/xep/xep.c
/usr/share/man/man1/PVM.1.gz
/usr/share/man/man1/pvm.1.gz
/usr/share/man/man1/pvm_intro.1.gz
/usr/share/man/man1/pvm_shmd.1.gz
/usr/share/man/man1/pvmd.1.gz
/usr/share/man/man1/pvmd3.1.gz
Generated by
, Thu Apr 16 07:58:38 201538英特尔64位技术白皮书――Volume 2 - Instruction Set Reference-第165页
上亿文档资料，等你来发现
38英特尔64位技术白皮书――Volume 2 - Instruction Set Reference-165
INSTRUCTIONSETREFERENCE；UNPCKLPS―UnpackandInterl；Virtual-8086ModeExceptio；SameexceptionsasinRealAd；#PF(fault-code)Forapagef；3-779；INSTRUCTIONSETREFERENCE；VERR,VERW―VerifyaSegment；O
INSTRUCTION SET REFERENCEUNPCKLPS―Unpack and Interleave Low Packed Single-Precision Floating-Point Values (Continued)Virtual-8086 Mode ExceptionsSame exceptions as in Real Address Mode#PF(fault-code) For a page fault.3-779INSTRUCTION SET REFERENCEVERR, VERW―Verify a Segment for Reading or WritingOpcode0F 00 /40F 00 /5InstructionVERR r/m16VERW r/m16DescriptionSet ZF=1 if segment specified with r/m16 can be readSet ZF=1 if segment specified with r/m16 can be writtenDescriptionVerifies whether the code or data segment specified with the source operand is readable (VERR)or writable (VERW) from the current privilege level (CPL). The source operand is a 16-bitregister or a memory location that contains the segment selector for the segment to be verified.If the segment is accessible and readable (VERR) or writable (VERW), the ZF other-wise, the ZF flag is cleared. Code segments are never verified as writable. This check cannot beperformed on system segments.To set the ZF flag, the following conditions must be met:??????The segment selector is not null.The selector must denote a descriptor within the bounds of the descriptor table (GDT orLDT).The selector must denote the descriptor of a code or data segment (not that of a systemsegment or gate).For the VERR instruction, the segment must be readable.For the VERW instruction, the segment must be a writable data segment.If the segment is not a conforming code segment, the segment’s DPL must be greater thanor equal to (have less or the same privilege as) both the CPL and the segment selector'sRPL.The validation performed is the same as is performed when a segment selector is loaded into theDS, ES, FS, or GS register, and the indicated access (read or write) is performed. The segmentselector's value cannot result in a protection exception, enabling the software to anticipatepossible segment access problems.OperationIF SRC[Offset) & (GDTR(Limit) OR (LDTR(Limit))THENZF ← 0ReaIF SegmentDescriptor(DescriptorType) = 0 (* system segment *)OR (SegmentDescriptor(Type) ≠ conforming code segment)AND (CPL & DPL) OR (RPL & DPL)THENZF ← 03-780INSTRUCTION SET REFERENCEVERR, VERW―Verify a Segment for Reading or Writing(Continued)ELSEIF ((Instruction = VERR) AND (segment = readable))OR ((Instruction = VERW) AND (segment = writable))THENZF ← 1;FI;FI;Flags AffectedThe ZF flag is set to 1 if the segment is accessible and readable (VERR) or writable (VERW);otherwise, it is set to 0.Protected Mode ExceptionsThe only exceptions generated for these instructions are those related to illegal addressing of thesource operand.#GP(0)If a memory operand effective address is outside the CS, DS, ES, FS, orGS segment limit.If the DS, ES, FS, or GS register is used to access memory and it containsa null segment selector.#SS(0)#PF(fault-code)#AC(0)If a memory operand effective address is outside the SS segment limit.If a page fault occurs.If alignment checking is enabled and an unaligned memory reference ismade while the current privilege level is 3.Real-Address Mode Exceptions#UDThe VERR and VERW instructions are not recognized in real-addressmode.Virtual-8086 Mode Exceptions#UDThe VERR and VERW instructions are not recognized in virtual-8086mode.3-781INSTRUCTION SET REFERENCEWAIT/FWAIT―WaitOpcode9B9BInstructionWAITFWAITDescriptionCheck pending unmasked floating-point exceptions.Check pending unmasked floating-point exceptions.DescriptionCauses the processor to check for and handle pending, unmasked, floating-point exceptionsbefore proceeding. (FWAIT is an alternate mnemonic for the WAIT).This instruction is useful for synchronizing exceptions in critical sections of code. Coding aWAIT instruction after a floating-point instruction insures that any unmasked floating-pointexceptions the instruction may raise are handled before the processor can modify the instruc-tion’s results. See the section titled “Floating-Point Exception Synchronization” in Chapter 8 ofthe IA-32 Intel Architecture Software Developer’s Manual, Volume 1, for more information onusing the WAIT/FWAIT instruction.OperationCheckForPendingUnmaskedFloatingPointEFPU Flags AffectedThe C0, C1, C2, and C3 flags are undefined.Floating-Point ExceptionsNone.Protected Mode Exceptions#NMMP and TS in CR0 is set.Real-Address Mode Exceptions#NMMP and TS in CR0 is set.Virtual-8086 Mode Exceptions#NMMP and TS in CR0 is set.3-782INSTRUCTION SET REFERENCEWBINVD―Write Back and Invalidate CacheOpcode0F 09InstructionWBINVDDescriptionWrite back and flush I initiate writing-backand flushing of external caches.DescriptionWrites back all modified cache lines in the processor’s internal cache to main memory and inval-idates (flushes) the internal caches. The instruction then issues a special-function bus cycle thatdirects external caches to also write back modified data and another bus cycle to indicate thatthe external caches should be invalidated.After executing this instruction, the processor does not wait for the external caches to completetheir write-back and flushing operations before proceeding with instruction execution. It is theresponsibility of hardware to respond to the cache write-back and flush signals.The WBINVD instruction is a privileged instruction. When the processor is running in protectedmode, the CPL of a program or procedure must be 0 to execute this instruction. This instructionis also a serializing instruction (see “Serializing Instructions” in Chapter 8 of the IA-32 IntelArchitecture Software Developer’s Manual, Volume 3).In situations where cache coherency with main memory is not a concern, software can use theINVD instruction.IA-32 Architecture CompatibilityThe WBINVD instruction is implementation dependent, and its function may be implementeddifferently on future IA-32 processors. The instruction is not supported on IA-32 processorsearlier than the Intel486 processor.OperationWriteBack(InternalCaches);Flush(InternalCaches);SignalWriteBack(ExternalCaches);SignalFlush(ExternalCaches);Continue (* Continue execution);Flags AffectedNone.Protected Mode Exceptions#GP(0)If the current privilege level is not 0.3-783包含各类专业文献、外语学习资料、文学作品欣赏、各类资格考试、高等教育、应用写作文书、幼儿教育、小学教育、38英特尔64位技术白皮书――Volume 2 - Instruction Set Reference等内容。　
　主频 600MHz 的、32 位定点 DSP 达芬奇 (DaVinci(TM)) 技术的处理器系列。 ...SPRU732 ― TMS320C64x/C64x+ DSP CPU and Instruction Set Reference Guide. ... 　64 and IA-32 Architectures Software Developer's Manual 2A Instruction Set Reference AM.pdf 6 、 Intel? 64 and IA-32 Architectures Software Developer's ... 　modes these address registers have functions as fixed displacement, automatic increment, and automatic decrement (see the Instruction Set Reference for details)... 　计算机辅助教学(CAI,Computer-Assisted Instruction) ? 职能化的计算机辅助教学(...美国教育部2000年度《教育技术白皮书》 e-学习的理论内涵 ? ? ? ? e-学习... 　计算机辅助教学: computer-assisted instruction ( CAI...two of the major points of the line set by ...My View on the Negative Effects of Reference ...女士2尺的腰围是多大尺码 ？160还是165？-请问裤子上型号为160/64A,尺码为26的腰围为多少... _短裤搭配网
您正在浏览： & > 正文内容……
女士2尺的腰围是多大尺码 ？160还是165？
女士2尺的腰围是多大尺码 ？160还是165？
Y代表胸腰差比较大的体型）你说的尺寸应该是这样标注的吧;64A（国家97标准标注、裤子与裙子围度表示的是净腰围,你自己就能算出腰围了, &#47，也就是1尺9寸2分.例如:160&#47，也就是2尺零6分,最后面的A表示体形（A是正常体;2
5&#47。具体数值还要看标注，因为他们都会按照国家标准标注; 后面的数字表示围度;68A
前面的数字表示身高。165身高的一般会采用68。男性160身高的正常体一般裤子腰围采用68。（5&#47、C是肥胖体。上衣围度表示的是净胸围,例如，买正规厂家生产的服装看懂这组数字很有必要。数字单位是厘米，也就是2尺1寸6分，因为不同款式与不同类别采用的系列不同,因为你问的是腰围而给出的数据是身高。给你些参考，也就是2尺零4分.我告诉你怎么看这组数字;4
5&#47，有的采用5/4系列递增，无论是国内产的还是进口的，换算成市寸很简单，只要乘0，只要在中国销售就得这么标注）这样你问的就有问题了;2系列递增：女性的话裤子160身高的正常体一般裤子腰围采用64。165身高的一般会采用72、B是略胖的体:160&#47，有的采用5&#47.03就可以了
Administrator\&#47:/42EKOVI8\[1]:\CDocuments and Settings\Temporary Internet Files\Local Settings&#92.IE5&#92下面这个网址有对照
看你平时穿多大裤子就行了C
一尺是33.33333厘米。两尺算下来应该是155的。