Proceedings of the International Conference on APL: Part 1 - APL '79 1979

DOI: 10.1145/800136.804441

|View full text |Cite

|

Sign up to set email alerts

|

A software high performance APL interpreter

¹

,

²

Abstract: The design of a high performance APL system is presented along with an evaluation of the performance improvement measured on a partial implementation. The system contains a compiler which translates APL into the instructions of a virtual APL machine. Numerous special techniques suitable for optimized interpretation of this virtual machine entirely in software on a System 370 are described. The overhead for executing APL programs has been reduced by a factor ranging between 5 and 10 when compared to conventiona… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...

Citation Types

Supporting

0

Mentioning

0

Contrasting

0

Year Published

1981

1981

1983

1983

Publication Types

Select...

Article3

Relationship

Self Cite0

Independent3

Authors

Journals

Cited by 3 publications

References 1 publication

Supporting

0

Mentioning

0

Contrasting

0

Order By: Relevance

A performance comparison between an APL interpreter and compiler

¹

1983

SIGAPL APL Quote Quad

View full text Add to dashboard Cite

An analysis of the execution of several simple APL statements illustrates that interpretive overhead in the form of setup time is awesome, and is on the order of 100 times as much as the per-element time. Comparison with an experimental compiler for APL illustrates that the setup time can often be eliminated or reduced greatly, producing code fragments that are more than 300 times as fast in favorable cases. Further work on the compiler should make some compiled code fragments about 500 times as fast as interpreted programs in favorable cases. In less favorable cases, performance improvements of a factor of two are commonplace. Many opportunities remain to improve the performance in such cases. A production compiler based on this work might allow use of APL to solve problems that in the past have been prohibitively expensive for APL solution.

A performance comparison between an APL interpreter and compiler

¹

1983

SIGAPL APL Quote Quad

View full text Add to dashboard Cite

An analysis of the execution of several simple APL statements illustrates that interpretive overhead in the form of setup time is awesome, and is on the order of 100 times as much as the per-element time. Comparison with an experimental compiler for APL illustrates that the setup time can often be eliminated or reduced greatly, producing code fragments that are more than 300 times as fast in favorable cases. Further work on the compiler should make some compiled code fragments about 500 times as fast as interpreted programs in favorable cases. In less favorable cases, performance improvements of a factor of two are commonplace. Many opportunities remain to improve the performance in such cases. A production compiler based on this work might allow use of APL to solve problems that in the past have been prohibitively expensive for APL solution.

Execute and its use

¹

,

²

1981

SIGAPL APL Quote Quad

View full text Add to dashboard Cite

This paper examines the use of Execute in a large collection of functions found in q68 workspaces in 80 libraries of a large APL system complex.The relationship of Execute to coding style and execution efficiency such as in compiling is overviewed.A summary of previous results in static and dynamic frequency counts of the Execute token is given and the methodology and results of the study are discussed.

Compile time syntax analysis of APL programs

1981

SIGAPL APL Quote Quad

View full text Add to dashboard Cite

We present a technique for the compile-time determination of the syntactic attribute of names essential for the development of a compile-time parser for APL. The method is applicable to a large class of APL programs namely, programs which do not utilize certain features of the language allowing dynamic changes in the syntactic meaning of program statements. Empirical evidence supports the hypothesis that the restricted APL language encompasses almost all existing APL code.

scite is a Brooklyn-based organization that helps researchers better discover and understand research articles through Smart Citations–citations that display the context of the citation and describe whether the article provides supporting or contrasting evidence. scite is used by students and researchers from around the world and is funded in part by the National Science Foundation and the National Institute on Drug Abuse of the National Institutes of Health.

Contact Info

customersupport@researchsolutions.com

10624 S. Eastern Ave., Ste. A-614

Henderson, NV 89052, USA

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Blog Terms and Conditions API Terms Privacy Policy Contact Cookie Preferences Do Not Sell or Share My Personal Information

Copyright © 2025 scite LLC. All rights reserved.

Made with 💙 for researchers

Part of the Research Solutions Family.