Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.

R. R. Oldehoeft

dblp:53/3932 · also Rodney R. Oldehoeft · DBLP profile ↗
← Back
17ranked-venue papers
9as first author
0since 2021 · last 2006
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Systems, architecture and hardware · 8 · 4 first-authorSoftware engineering, systems software and programming languages · 8 · 4 first-authorHuman-computer interaction and ubiquitous computing · 1 · 1 first-author

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
6 papers
Programming languages and type systems · 26% Concurrent programming · 26% Debugging and program repair · 20%
Computer architecture, parallel and distributed computing, and storage systems
1 paper
Processor architecture and microarchitecture · 56% Parallel and multicore computing · 44%

Topics — the 11 heaviest of 13, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Concurrent programming › concurrency models
nondeterminism
0.011994
Two Issues in Parallel Language Design · ACM Trans. Program. Lang. Syst. 1994
Programming languages and type systems › language design
parallel language design
0.011994
Two Issues in Parallel Language Design · ACM Trans. Program. Lang. Syst. 1994
Processor architecture and microarchitecture
multithreading
0.011992
Multithreaded Computer Systems · SC 1992
Parallel and multicore computing
parallel programming models
0.011992
Multithreaded Computer Systems · SC 1992
Compilers and program optimization › compiler construction
compilation techniques
0.011987
DI: an interactive debugging interpreter for applicative languages · PLDI 1987
Debugging and program repair
debugging tools
0.011987
DI: an interactive debugging interpreter for applicative languages · PLDI 1987
Debugging and program repair › software debugging
interactive debugging
0.011987
DI: an interactive debugging interpreter for applicative languages · PLDI 1987
Processor architecture and microarchitecture
dataflow architecture
0.011992
Multithreaded Computer Systems · SC 1992
Program analysis
graph-based analysis
0.011983
Program Graphs and Execution Behavior · IEEE Trans. Software Eng. 1983
Empirical software engineering
software metrics
0.021979
Dynamic Software Science with Applications · IEEE Trans. Software Eng. 1979
A Contrast Between Language Level Measures · IEEE Trans. Software Eng. 1977
Program analysis
static analysis
0.011983
Program Graphs and Execution Behavior · IEEE Trans. Software Eng. 1983

Methods — techniques the papers use, named apart from their topics

split-phase memory access · 0.0multithreading · 0.0data matching · 0.0reference counting · 0.0graph interpretation · 0.0regular expression simplification · 0.0finite automaton · 0.0information theory · 0.0
YearPublicationVenuePosition
2006 Computer science in support of high-performance applications: Papers from the 2004 lacsi symposium
R. R. Oldehoeft
J. Supercomput.1
2002 Introduction to Software for High-Performance Systems Papers from the Symposium of The Los Alamos Computer Science Institute
R. R. Oldehoeft
J. Supercomput.1
1999 SMARTS: exploiting temporal locality and parallelism through vertical execution
abstract
Article SMARTS: exploiting temporal locality and parallelism through vertical execution Share on Authors: Suvas Vajracharya Los Alamos National Laboratory, Los Alamos, NM Los Alamos National Laboratory, Los Alamos, NMView Profile , Steve Karmesin Los Alamos National Laboratory, Los Alamos, NM Los Alamos National Laboratory, Los Alamos, NMView Profile , Peter Beckman Los Alamos National Laboratory, Los Alamos, NM Los Alamos National Laboratory, Los Alamos, NMView Profile , James Crotinger Los Alamos National Laboratory, Los Alamos, NM Los Alamos National Laboratory, Los Alamos, NMView Profile , Allen Malony Dept. of Computer and Information Science, University of Oregon and Los Alamos National Laboratory, Los Alamos, NM Dept. of Computer and Information Science, University of Oregon and Los Alamos National Laboratory, Los Alamos, NMView Profile , Sameer Shende Dept. of Computer and Information Science, University of Oregon and Los Alamos National Laboratory, Los Alamos, NM Dept. of Computer and Information Science, University of Oregon and Los Alamos National Laboratory, Los Alamos, NMView Profile , Rod Oldehoeft Los Alamos National Laboratory, Los Alamos, NM Los Alamos National Laboratory, Los Alamos, NMView Profile , Stephen Smith Los Alamos National Laboratory, Los Alamos, NM Los Alamos National Laboratory, Los Alamos, NMView Profile Authors Info & Claims ICS '99: Proceedings of the 13th international conference on SupercomputingJune 1999 Pages 302–310https://doi.org/10.1145/305138.305207Online:01 May 1999Publication History 16citation354DownloadsMetricsTotal Citations16Total Downloads354Last 12 Months4Last 6 weeks0 Get Citation AlertsNew Citation Alert added!This alert has been successfully added and will be sent to:You will be notified whenever a record that you have chosen has been cited.To manage your alert preferences, click on the button below.Manage my AlertsNew Citation Alert!Please log in to your account Save to BinderSave to BinderCreate a New BinderNameCancelCreateExport CitationPublisher SiteGet Access
Suvas Vajracharya, Steve Karmesin, Pete Beckman, James Crotinger, Allen D. Malony, Sameer Shende, R. R. Oldehoeft, Stephen Smith 0002
International Conference on Supercomputing7
1994 Two Issues in Parallel Language Design
abstract
In this article, we discuss two programming language features that have value for expressibility and efficiency: nonstrictness and nondeterminism. Our work arose while assessing ways to enhance a currently successful language, SISAL [McGraw et al. 1985]. The questions of how best to include these features, if at all, has led not to conclusions but to an impetus to explore the answers in an objective way. We will retain strictness for efficiency reasons and explore the limits it may impose, and we will experiment with a carefully controlled form of nondeterminism to assess its expressive power.
A. P. Wim Böhm, R. R. Oldehoeft
ACM Trans. Program. Lang. Syst.2
1992 Multithreaded Computer Systems
abstract
In this minisymposium speakers address architectural principles and issues of multithreaded computer systems, examine approaches to providing implicitly parallel software for these machines, and give an industrial perspective that includes the potential wider influence of multithreaded computers. Multithreaded computer systems are parallel machines in which threads are sequentially executed code segments. Each processor has hardware support for quickly switching contexts among runnable threads. Other features include some form of data matching, split-phase memory accesses, and a dataflow-like regime for thread instantiation. They combine features of conventional von Neumann systems with those of fine-grained dataflow architectures.>
R. R. Oldehoeft
SC1
1990 A Report on the Sisal Language Project
John Feo, David C. Cann, R. R. Oldehoeft
J. Parallel Distributed Comput.3
1990 Mixed applicative and imperative programs
R. R. Oldehoeft, James R. McGraw
Parallel Comput.1
1987 DI: an interactive debugging interpreter for applicative languages
abstract
The DI interpreter is both a debugger and interpreter of SISAL programs. Its use as a program interpreter is only a small part of its role; it is designed to be a tool for studying compilation techniques for applicative languages. DI interprets dataflow graphs expressed in the IF1 and IF2 languages, and is heavily instrumented to report the activity of dynamic storage activity, reference counting, copying and updating of structured data values. It also aids the SISAL language evaluation by providing an interim execution vehicle for SISAL programs. DI provides determinate, sequential interpretation of graph nodes for sequential and parallel operations in a canonical order. As a debugging aid, DI allows tracing, breakpointing, and interactive display of program data values. DI handles creation of SISAL and IF1 error values for each data type and propagates them according to a well-defined algebra. We have begun to implement IF1 optimizers and have measured the improvements with DI.
Stephen K. Skedzielewski, Robert Kim Yates, R. R. Oldehoeft
PLDI3
1985 Parallel Dynamic Storage Allocation
Bruce M. Bigler, Stephen J. Allan, R. R. Oldehoeft
ICPP3
1983 A Stream Definition for Von Neumann Multiprocessors
Stephen J. Allan, R. R. Oldehoeft
ICPP2
1983 Program Graphs and Execution Behavior
abstract
This paper describes a technique for predicting the execution behavior of a source program or a software design specification. As a by-product of syntactic analysis, a program graph is constructed which can subsequently be treated as the graph of a finite automaton. The expression for execution behavior is the regular expression of the graph. Several simplification techniques for these expressions are discussed and exemplified. In particular, the substitution of known values for program segments followed by constant folding cannot be done indiscriminately; the allowable situations are characterized. Applications include the prediction of execution time for a program or a software design, other forms of language analysis, and program restructuring.
R. R. Oldehoeft
IEEE Trans. Software Eng.1
1981 An Interactive Manager for Pascal Software
abstract
Abstract An interactive facility for development and maintenance of Pascal programs is described. Features include interactive addition, deletion and modification of modules, independentcompilation of groups of procedures, and automatic recompilation of an entire program only if global declarations are modified. The implementation required modification of a Pascal compiler to process an arbitrary number of programs in a single run and to compile correctly if the main program is missing. Overall processing is managed by a parameterized control statement procedure that invokes several system utilities. The facility has been used successfully in instructional and research computing situations. Significant remaining problems are errors caused by mismatched parameters between independently compiled procedures, and interpretation by users of error messages generated by system utilities.
R. R. Oldehoeft, W. D. Ralph, M. H. Tindall
Softw. Pract. Exp.1
1979 Dynamic Software Science with Applications
abstract
Two disciplines have been developed during the past few years for the study of computer software. Software physics has as its purpose the analysis of execution characteristics of programs. Basic measures of software work, time, and shortage occupancy are used to derive measures such as power, capacity usage, and storage work, with applications to the choice of processor and device speeds. Software science is related to information theory. Occurrences of operators and operands in the text of programs are counted to provide measures for a number of relationships; among them are estimates for program length, program and language level, and programming time.
R. R. Oldehoeft, Leonard J. Bass
IEEE Trans. Software Eng.1
1977 Methodology for teaching introductory computer science
abstract
In the last few years it has been generally recognized that teaching programming involves more than describing a new FORTRAN statement each day and providing programming problems to be coded. The concepts of disciplined programming and the accompanying interest in the problem solving process, coupled with the increasing economic desirability of constructing correct and maintainable software has resulted in significant attention being focused on what should be taught, and, to a lesser extent, on how this is best accomplished.
R. R. Oldehoeft, R. V. Roman
SIGCSE-11
1977 Success and Failure Analysis of a Problem Solving System Implementation
abstract
Abstract The NAPSS (Numerical Analysis Problem Solving System) project was an attempt to develop an interactive system, with a high‐level language resembling conventional mathematics, for solving problems in numerical analysis. This report uses NAPSS as an example to discuss some aspects of the design and implementation of the programming languages and software which comprise problem solving systems. Successful features as well as failures (with alternative proposals) are detailed in the areas of general language management, specific language features and the operating system interface. In general, a massive, coherent implementation of theoretical work being done at the frontiers of research has abundant opportunity for failure.
Lawrence R. Symes, R. R. Oldehoeft
Softw. Pract. Exp.2
1977 A Contrast Between Language Level Measures
abstract
Software science techniques have been used to provide a framework for evaluation of problem solving systems. In that effort, two methods for calculating the level of a language (L and L̂) were used, it was suspected that L̂, while adequate in that application, might be inferior to L. By using a set of hypothetical languagesj each with different intrinsic data structures and operators, it is shown here that when an inappropriate language is applied to some problems, L̂ may reflect an inaccurately large value for language level, and can sometimes be made to yield an arbitrary value. Since L is often as easily applied as L, and does not exhibit this anomalous behavior, it is suggested that its general use is to be preferred.
R. R. Oldehoeft
IEEE Trans. Software Eng.1
1977 Context of Problem-Solving Systems
abstract
Considerable effort has been expanded in attempts to combine the power found in algorithmic languages with the power found in program libraries. However, most of these attempts to construct problem-solving systems for a particular class of users have failed to achieve their objective of providing the user with the potential benefits inherent in such systems. This paper attempts to define and place problem-solving systems in a general context, and thereby shows when the potential for failure or success is high.
Lawrence R. Symes, R. R. Oldehoeft
IEEE Trans. Software Eng.2