Results 1 -
8 of
8
Coupling Hundreds of Workstations for Parallel Molecular Sequence Analysis
, 1995
"... this paper, we show the possibility and describe how we employed a distributed workstation network of more than 800 machines, geographically scattered over all continents, to accelerate a computational problem that fits the capabilities of this system's architecture. The computing challenge of molec ..."
Abstract
-
Cited by 8 (1 self)
- Add to MetaCart
this paper, we show the possibility and describe how we employed a distributed workstation network of more than 800 machines, geographically scattered over all continents, to accelerate a computational problem that fits the capabilities of this system's architecture. The computing challenge of molecular biology sequence analysis, one of the key techniques of the Human Genome projects, 4,5 is accelerated from run-times of a couple of days on a single workstation or Cray processor to some minutes with our platform
Notes on Writing Portable Programs In C
, 2000
"... This document is in the public domain. Email address (Internet) are ado@sauna.hut.fi (preferred contact) and arl@sauna.hut.fi, respectively ..."
Abstract
-
Cited by 1 (0 self)
- Add to MetaCart
This document is in the public domain. Email address (Internet) are ado@sauna.hut.fi (preferred contact) and arl@sauna.hut.fi, respectively
Notes on Writing Portable Programs in C
, 1995
"... This documents describes the features and non-features of different C preprocessors, compilers, and environments. As such, it is an incomplete document, growing as information is gathered. It contains some material concerning ANSI C but it is not a substitute for the Standard itself; neither are rel ..."
Abstract
- Add to MetaCart
This documents describes the features and non-features of different C preprocessors, compilers, and environments. As such, it is an incomplete document, growing as information is gathered. It contains some material concerning ANSI C but it is not a substitute for the Standard itself; neither are related textbooks. We assume the reader is familiar with the C programming language. Internet: ado@sauna.hut.fi. y Internet: pardo@cs.washington.edu. z Internet: gvr@cs.brown.edu. 2 Contents 1 Foreword 4 2 Introduction 4 3 Standardization Efforts 5 3.1 ANSI C : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 5 3.1.1 Translation Limits : : : : : : : : : : : : : : : : : : : : 5 3.1.2 Unspecified and Undefined Behavior : : : : : : : : : : 7 3.2 POSIX : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 7 4 Preprocessors 7 4.1 Command Options : : : : : : : : : : : : : : : : : : : : : : : : 8 4.2 #pragma and #elif : : : : : : : : : : : : : : : : : : : : : : : : 8 4.3 ...
Style and organization rules for C programs how to enjoy freedom without stress
"... The aim of this document is to present a coherent set of prescriptions about the style, the organization, the documentation and the precautions to be used while developing software in C language. These specifications are particularly important for projects that require the integration and the re-use ..."
Abstract
- Add to MetaCart
The aim of this document is to present a coherent set of prescriptions about the style, the organization, the documentation and the precautions to be used while developing software in C language. These specifications are particularly important for projects that require the integration and the re-use of software modules developed in a scientific research context by different institutions and people, possibly at different times. While C is a widely used language with a rich availability of compilers, the software designer and developer must be fully aware of the "low-level" nature of the language, that was born without extensive support for modularity, type checking, etc. It is therefore the responsibility of the designer to assure a high modularity and provisions for documentation, easy maintenance, and re-use. The suggested rules are the result of an analysis of widely adopted rules for "literate" C programming. Contents Introduction 1 1 The Code 3 1.1 Human semantic aspects : : :...
Wux: Unix Tools under Windows
- In USENIX Conference Proceedings
, 1994
"... Wux is a port of Unix tools to the Microsoft Windows environment. It is based on a library providing a Unixcompatible set of system calls on top of Windows. Unix-derived tools run in parallel, communicating using the Unix pipe abstraction. All processes are run within an application template that gi ..."
Abstract
- Add to MetaCart
Wux is a port of Unix tools to the Microsoft Windows environment. It is based on a library providing a Unixcompatible set of system calls on top of Windows. Unix-derived tools run in parallel, communicating using the Unix pipe abstraction. All processes are run within an application template that gives them basic Windows compatibility such as input and output windows and an icon. The performance of the system is comparable to that of Unix ports to the PC architecture. 1 Motivation The Unix operating system offers a wide variety of tools that can be used as building blocks or autonomous units for application development. Although these and similar tools can be ported to other environments [KP76, Gor93], their usability is often impaired by the lack of the glue elements available under Unix: multitasking and interprocess communication using pipes. Specifically, tool ports to the widely used MS-DOS system have to rely on serialised process execution and pipes implemented using inefficie...
Notes on Writing Portable Programs in C
, 1995
"... This documents describes the features and non-features of different C preprocessors, compilers, and environments. As such, it is an incomplete document, growing as information is gathered. It contains some material concerning ANSI C but it is not a substitute for the Standard itself; neither are ..."
Abstract
- Add to MetaCart
This documents describes the features and non-features of different C preprocessors, compilers, and environments. As such, it is an incomplete document, growing as information is gathered. It contains some material concerning ANSI C but it is not a substitute for the Standard itself; neither are related textbooks. We assume the reader is familiar with the C programming language. Internet: ado@sauna.hut.fi. y Internet: pardo@cs.washington.edu. z Internet: gvr@cs.brown.edu. 1 2 Contents 1 Foreword 4 2 Introduction 4 3 Standardization Efforts 5 3.1 ANSI C : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 5 3.1.1 Translation Limits : : : : : : : : : : : : : : : : : : : : 5 3.1.2 Unspecified and Undefined Behavior : : : : : : : : : : 7 3.2 POSIX : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 7 4 Preprocessors 7 4.1 Command Options : : : : : : : : : : : : : : : : : : : : : : : : 8 4.2 #pragma and #elif : : : : : : : : : : : : : : : : : : : : : : : : 8 4...

