PRT.UnivDevelop History
Hide minor edits - Show changes to output - Cancel
Changed line 3 from:
Development related to PRT covers many different kinds of projects, from writing benchmarks and applications, to creating languages on top of PRT, to modifying PRT itself. To satisfy the needs of developers of each different kind of project, an individual project has been organized as a collection of sub-repositories. A top-level repository has a list of all the sub-repositories, and cloning the top will clone all the sub-repos, and update each to a particular version. Notes on a variety of aspects of PRT related development can be found in the pages linked below -- note, however, that this site is in flux, and many of these pages are old, dating back to the original version of proto-runtime, which was called VMS, so some of the information may differ from how PRT-Univ is developed. The URL will contain "VMS" if the page is old:
to:
Development related to PRT covers many different kinds of projects, from writing benchmarks and applications, to creating languages on top of PRT, to modifying PRT itself. To satisfy the needs of developers of each different kind of project, an individual project has been organized as a collection of sub-repositories. A top-level repository has a list of all the sub-repositories, and cloning the top will clone all the sub-repos, and update each to a particular version. Notes on a variety of aspects of PRT related development can be found in the pages linked below -- note, however, that this site is in flux, and many of these pages are old, dating back to the original version of proto-runtime, which was called VMS, so some of the information may differ from how PRT-Univ is developed. The page will have the "VMS" logo at the top if the page is old:
Changed line 3 from:
Development related to PRT covers many different kinds of projects, from writing benchmarks and applications, to creating languages on top of PRT, to modifying PRT itself. To satisfy the needs of developers of each different kind of project, an individual project has been organized as a collection of sub-repositories. A top-level repository has a list of all the sub-repositories, and cloning the top will clone all the sub-repos, and update each to a particular version. Notes on a variety of aspects of PRT related development can be found in the pages linked below -- note, however, that this site is in flux, and many of these pages are old, dating back to the original version of proto-runtime, which was called VMS, so some of the information may differ from how PRT-Univ is developed:
to:
Development related to PRT covers many different kinds of projects, from writing benchmarks and applications, to creating languages on top of PRT, to modifying PRT itself. To satisfy the needs of developers of each different kind of project, an individual project has been organized as a collection of sub-repositories. A top-level repository has a list of all the sub-repositories, and cloning the top will clone all the sub-repos, and update each to a particular version. Notes on a variety of aspects of PRT related development can be found in the pages linked below -- note, however, that this site is in flux, and many of these pages are old, dating back to the original version of proto-runtime, which was called VMS, so some of the information may differ from how PRT-Univ is developed. The URL will contain "VMS" if the page is old:
Changed lines 1-3 from:
!!Welcome to the VMS Development Area
Development related to VMS covers many different kinds of projects, from writing benchmarks, to creating languages, to extending VMS. To keep things manageable and straight forward for the various developers, each aspect of development has been given its own project. A project consists of a top-level repository and a number of sub-repositories. Notes on a variety of aspects of VMS related development can be found in the pages linked below:
Development related to VMS covers many different kinds of projects, from writing benchmarks
to:
!!Welcome to the Development Area for PRT Universal
Development related to PRT covers many different kinds of projects, from writing benchmarks and applications, to creating languages on top of PRT, to modifying PRT itself. To satisfy the needs of developers of each different kind of project, an individual project has been organized as a collection of sub-repositories. A top-level repository has a list of all the sub-repositories, and cloning the top will clone all the sub-repos, and update each to a particular version. Notes on a variety of aspects of PRT related development can be found in the pages linked below -- note, however, that this site is in flux, and many of these pages are old, dating back to the original version of proto-runtime, which was called VMS, so some of the information may differ from how PRT-Univ is developed:
Development related to PRT covers many different kinds of projects, from writing benchmarks and applications, to creating languages on top of PRT, to modifying PRT itself. To satisfy the needs of developers of each different kind of project, an individual project has been organized as a collection of sub-repositories. A top-level repository has a list of all the sub-repositories, and cloning the top will clone all the sub-repos, and update each to a particular version. Notes on a variety of aspects of PRT related development can be found in the pages linked below -- note, however, that this site is in flux, and many of these pages are old, dating back to the original version of proto-runtime, which was called VMS, so some of the information may differ from how PRT-Univ is developed:
Added line 10:
* [[VMS.DevelopLearnCode | Learning the code base]]
Changed line 10 from:
* [[VMS.DevelopPatterns | Patterns to use while developing VMS projects]]
to:
* [[VMS.DevelopPatterns | Patterns for directory structure, naming, and so on, to use while developing VMS projects]]
Changed line 3 from:
Development related to VMS covers many different kinds of projects, from writing benchmarks, to creating languages, to extending VMS. To keep things manageable and straight forward for the various developers, each aspect of development has been given its own project. A consists of a top-level repository and a number of sub-repositories. Notes on a variety of aspects of VMS related development can be found in the pages linked below:
to:
Development related to VMS covers many different kinds of projects, from writing benchmarks, to creating languages, to extending VMS. To keep things manageable and straight forward for the various developers, each aspect of development has been given its own project. A project consists of a top-level repository and a number of sub-repositories. Notes on a variety of aspects of VMS related development can be found in the pages linked below:
Changed line 3 from:
Development related to VMS covers many different kinds of projects, from writing benchmarks, to creating languages, to extending VMS. To keep things manageable and straight forward for the various developers, each aspect of development has been given its own project, which consists of a top-level repository and a number of sub-repositories. Notes on a variety of aspects of VMS related development can be found in the pages linked below:
to:
Development related to VMS covers many different kinds of projects, from writing benchmarks, to creating languages, to extending VMS. To keep things manageable and straight forward for the various developers, each aspect of development has been given its own project. A consists of a top-level repository and a number of sub-repositories. Notes on a variety of aspects of VMS related development can be found in the pages linked below:
Added lines 3-8:
Development related to VMS covers many different kinds of projects, from writing benchmarks, to creating languages, to extending VMS. To keep things manageable and straight forward for the various developers, each aspect of development has been given its own project, which consists of a top-level repository and a number of sub-repositories. Notes on a variety of aspects of VMS related development can be found in the pages linked below:
!!!Individual Projects
* [[VMS.DevelopProjectNotes|A list of pages with notes about the projects, one for each project]]
* [[VMS.DevelopGetProject | Generic instructions on getting a project and configuring it]]
!!!Individual Projects
* [[VMS.DevelopProjectNotes|A list of pages with notes about the projects, one for each project]]
* [[VMS.DevelopGetProject | Generic instructions on getting a project and configuring it]]
Deleted line 13:
Deleted line 20:
Added line 16:
* [[VMS.DevelopProjectNotes|Notes about individual projects]]
Changed line 11 from:
* [[http://hg.opensourceresearchinstitute.org/cgi-bin/hgwebdir.cgi/VMS/2__runs_and_data/|The repository for run results, configuration files, and input files]]
to:
* [[VMS.DevelopRunsAndDataRepo|The repository for run results, configuration files, and input files]]
Changed lines 11-12 from:
to:
* [[http://hg.opensourceresearchinstitute.org/cgi-bin/hgwebdir.cgi/VMS/2__runs_and_data/|The repository for run results, configuration files, and input files]]
Changed line 22 from:
* [[VMS.IntellMICArch | MIC architecture]]
to:
* [[VMS.IntellMICArch | MIC architecture]]
Added line 14:
* [[VMS.DevelopVisualTool| Using the performance visualizer]]
Added lines 14-16:
!!!Research Ideas
* [[VMS.DevelopSchedulers|Scheduler Research]]
Added line 8:
* [[VMS.DevelopGetProject | Getting a project and configuring it]]
Deleted line 10:
Added line 5:
* [[VMS.DevelopDebug| Tips on debugging Applications, languages, and VMS itself]]
Added line 9:
* [[VMS.DevelopGetProject | Getting a project and configuring it]]
Deleted lines 5-7:
* [[VMS.DevelopPerformanceCounters| Using performance counters]]
Added lines 9-11:
!!! Implementation Details
* [[VMS.DevelopPerformanceCounters| Using performance counters]]
Added line 5:
* [[VMS.DevelopPatterns | Patterns to use while developing VMS projects]]
Added lines 1-9:
!!Welcome to the VMS Development Area
!!!Development Practices
* [[VMS.DevelopPractices | Development Practices]]
!!! Implementation Details
* [[VMS.DevelopPerformanceCounters| Using performance counters]]
!!!Repositories
!!!Development Practices
* [[VMS.DevelopPractices | Development Practices]]
!!! Implementation Details
* [[VMS.DevelopPerformanceCounters| Using performance counters]]
!!!Repositories
Added lines 12-13:
!!!Intelligence Gathering
Changed line 15 from:
* [[VMS.IntellMICArch | MIC architecture]]
to:
* [[VMS.IntellMICArch | MIC architecture]]
Changed lines 3-4 from:
* [[VMS.IntellSCC | SCC architecture]]
to:
* [[VMS.IntellSCC | SCC architecture]]
* [[VMS.IntellMICArch | MIC architecture]]
* [[VMS.IntellMICArch | MIC architecture]]
Deleted line 0:
Changed lines 2-3 from:
* [[VMS.DevelopCreateRepository | creating a repository]]
to:
* [[VMS.DevelopCreateRepository | creating a repository]]
* [[VMS.IntellSCC | SCC architecture]]
* [[VMS.IntellSCC | SCC architecture]]
Changed lines 1-3 from:
* [[VMS.Develop_CreateRepository | creating a repository]]
to:
* [[VMS.DevelopRepositoryStructure | Repository Structure and Usage]]
* [[VMS.DevelopCreateRepository | creating a repository]]
* [[VMS.DevelopCreateRepository | creating a repository]]
Changed line 1 from:
* [[VMS.Develop.CreateRepository | creating a repository]]
to:
* [[VMS.Develop_CreateRepository | creating a repository]]
Changed lines 1-2 from:
to:
* [[VMS.Develop.CreateRepository | creating a repository]]
Changed lines 2-3 from:
to:
* [[VMS.Develop/CreateRepository | creating a repository]]
Added lines 1-3:
* [[VMS/Develop/CreateRepository | creating a repository]]