Difference between revisions of "PTP/new and noteworthy/5.0.0"
(→Parallel Language Development Tools (PLDT))
|Line 59:||Line 59:|
=== New Refactorings ===
=== New Refactorings ===
=== Bug Fixes ===
=== Bug Fixes ===
Revision as of 10:03, 24 May 2011
Please add new features in PTP 5.0 here and we'll build our N&N/help item from this. Images too please!
"New and Noteworthy" is a tradition for Eclipse projects - an interesting way to present our new features. Screenshots and enticing examples are best! But any information at all is welcome - we can get screenshots later.
The PTP/new_and_noteworthy/4.0.0 is also available.
- 1 Eclipse IDE for Parallel Application Developers
- 2 PTP Resource Managers
- 3 Remote Development Tools (RDT)
- 4 Parallel Language Development Tools (PLDT)
- 5 Photran 7
- 6 External Tools Framework (ETFw)
- 7 Graphical Explorer of MPI Programs (GEM)
- 8 Parallel Performance Wizard (PPW)
Eclipse IDE for Parallel Application Developers
With this release of Eclipse (Indigo, 3.7) there is now an Eclipse package all-in-one download with the essentials for Parallel Application Developers:
- Eclipse CDT - basics of C/C++ development
- PTP - Core features of PTP
- Photran - Development Environment for Fortran
- RDT, Remote Development Tools
- CDT UPC features
- Some Linux Tools features not specific to Linux
- XML Editors and tools useful for creating new JAXB-based resource managers
- CVS and jGit
PTP Resource Managers
Remote Development Tools (RDT)
Parallel Language Development Tools (PLDT)
- Less intrusive/annoying insistence on setting MPI, OpenMP, preferences which were only used for non-prefix matching; more reliance on "prefix-only match" for artifacts, so these aren't really necessary now.
- More accurate location of artifacts including within macro expansions
Code templates make it easier to type common Fortran constructs. For example, by typing "pro", pressing Ctrl+Space, and then pressing Enter to choose the "program...end program" template, Photran will automatically fill in "program <name>" and "end program <name>" statements. As you type the program name, both the "program" and "end program" statements will be adjusted accordingly. Then, press the Enter key to begin filling in the body of the program.
"Correct Indentation" Command
Correct Indentation adjusts the indentation of the selected text in the editor (or the entire file if no text is selected). The current tab width (configured in the workspace preferences) is assumed to constitute one level of indentation.
Tabs-to-spaces conversion and custom tab width
It is now possible to set the "convert tabs to spaces" option in the Fortran editor without setting it workspace-wide. It is also possible to set a custom tab width for the Fortran editor.
New Horizontal Ruler
The Fortran editor has a new horizontal ruler. It looks a bit nicer, shows tab stops, and (unlike in previous versions) works in both the free- and fixed-form editors, even when folding is enabled.
19 New Refactorings
- Add Subroutine Parameter
- Permute Subroutine Arguments
- Safe Delete
- Fuse Loops
- Reverse Loop
- Tile Loop
- Unroll Loop
Refactorings to Remove Obsolete Constructs:
- Remove Arithmetic If-statement
- Remove Assigned Go To
- Remove Branch to End If
- Replace Character* with Character(len=)
- Remove Computed Goto
- Remove Old-Style Do-loops
- Remove Pause Statement
- Remove Real and Double Precision Loop Counters
Refactorings to Improve Coding Style:
- Add Identifier to End-statement
- Convert Between If-statement and If-construct
- Make Save Attributes Explicit
- Remove Unreferenced Labels
- Parser Bugs
- Managed Make
External Tools Framework (ETFw)
Graphical Explorer of MPI Programs (GEM)
Full GEM help documentation can be found online here
GEM now supports remote C/C++ MPI projects whose connections are through one of the following remote service providers:
- Remote Tools
- Remote System Explorer
Target Machine Requirements:
- ISP version 0.3.0 or later
- Some implementation of MPI must be installed, MPICH2 or OpenMPI both work well
GEM Browser View
This highly functional view summarizes and categorically groups all of the errors and warnings found by GEM on a particular MPI verification run. The summary label (just above the tabs) gives the user a quick overview of problems found. Errors and warnings are mapped to the corresponding source code lines in the Eclipse editor. The Browser View's tabs help the user to quickly locate and fix MPI errors flagged by GEM in their source code. Full documentation for the GEM Browser View is here
Figure 1 below shows what the Browser View should look like along with an explanation of its components.
Browser View Tabs
Below the GEM Browser summary label (the line above the tabs summarizing the errors and warnings found) is a section containing a tab for category of error or warning that was found in the code. By selecting a particular tab the user is given detailed information on each occurrence of that type of error or warning in their MPI code. Clicking on any of these occurrences takes the user to the offending line in the source code within the Eclipse editor. If there are no instances of the problem then there is a short message indicating as much. Furthermore, a user is shown which types of errors are present via the icons of the tab (see icons directly below).
This tab allows the user to visit all of the calls that did not complete due to each detected deadlock.
This tab list all local assertion violations found. Clicking any one of these will take the user to the line of source code with the failed assertion.
Clicking any of these will take the user to the line of source code where the corresponding un-freed MPI resource was allocated (these are usually MPI communicators and MPI DataTypes).
This tab is reserved for Functionally Irrelevant Barriers. Clicking any these will take the user to the corresponding MPI_Barrier call itself, which can then be safely removed without changing the runtime behavior of the program. This could potentially speed the application up with the absence of unnecessary synchronization.
These are warnings about the send type not matching the receive type. In some cases this may be intentional, but often times it is a programming mistake.
New Preference Pages
GEM now has two preference pages. (Full documentation is here).
GEM Preference Page
This preference page is for settings related to how the views and various components within GEM behave and function. Here the user can control which GEM Views are shown and when, e.g. the active view (the view in focus after verification is complete), can be set on the GEM Preference Page. (see Figure 2 below).
ISP Preference Page
This preference page is for command line settings for the underlying formal verification engine GEM uses, In-situ Parital Order (ISP).
Additions include the following options (see Figure 3 below):
- Use Unix Sockets This dramatically increases the speed in which GEM verifies your application if run on a local machine.
- Host Where ISP Resides This will allow the use of GEM in a distributed setting
Enhanced Console Output
The main enhancement to this view is that during a GEM verification run, this view is active and gives STDOUT and STDERR as it occurs instead of a single lump sum at the end of the verification run. GEM console output is now red for STDERR. These enhancements help the user to recognize what is happening as the verification is being done at runtime (a status bar of sorts).