{"title":"A dataflow-based APL for the hypercube","authors":"A. Mazer","doi":"10.1145/62297.62357","DOIUrl":null,"url":null,"abstract":"Traditional hypercube programming has three main characteristics. Most is done in a compiled language, FORTRAN or C, directly for the hypercube architecture and usually, one particular hypercube operating system. Secondly, algorithms have had very symmetrical decompositions; each node does essentially the same thing as other nodes. Similarly, data decomposition has normally been very regular, To an extent, these characteristics are very understandable. The people coding for the hypercube have been programmers writing code to solve problems suited to their particular hypercube as quickly as possible. The hypercube architecture is obviously well-suited to regular problems. The hypercube is reaching a stage of maturity, however, at which it’s appropriate to consider alternatives to these methods. In particular, compiled languages such as FORTRAN and C offer little to the casual user in the way of a convenient development environment or real-time feedback. Moreover, individual users must either build up and maintain a software library or recode commonly-used routines as they develop applications. The user must be familiar with the operating system interface to the hypercube, be willing to change code if the program needs to be ported, and be willing and able to convert the code into a parallel implementation.","PeriodicalId":299435,"journal":{"name":"Conference on Hypercube Concurrent Computers and Applications","volume":"21 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"2","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"Conference on Hypercube Concurrent Computers and Applications","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1145/62297.62357","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 2
Abstract
Traditional hypercube programming has three main characteristics. Most is done in a compiled language, FORTRAN or C, directly for the hypercube architecture and usually, one particular hypercube operating system. Secondly, algorithms have had very symmetrical decompositions; each node does essentially the same thing as other nodes. Similarly, data decomposition has normally been very regular, To an extent, these characteristics are very understandable. The people coding for the hypercube have been programmers writing code to solve problems suited to their particular hypercube as quickly as possible. The hypercube architecture is obviously well-suited to regular problems. The hypercube is reaching a stage of maturity, however, at which it’s appropriate to consider alternatives to these methods. In particular, compiled languages such as FORTRAN and C offer little to the casual user in the way of a convenient development environment or real-time feedback. Moreover, individual users must either build up and maintain a software library or recode commonly-used routines as they develop applications. The user must be familiar with the operating system interface to the hypercube, be willing to change code if the program needs to be ported, and be willing and able to convert the code into a parallel implementation.