Compilers: Difference between revisions
From Modelado Foundation
imported>ChunhuaLiao No edit summary |
imported>Schulzm (added PIPER) |
||
| Line 26: | Line 26: | ||
|(CORVETTE) | |(CORVETTE) | ||
|SLEEC | |SLEEC | ||
|( | |PIPER does not have/need its own compiler, but we need access to compiler generated information that captures high-level semantics of the language implemented (basically a form of DWARF for DSLs). Additionally, advanced instrumentation or instrumentation point/markers could be useful. | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
|'Program analysis can be both challenging and require specialized expertise. What requirements do you have for program analysis and what level of expertise you expect to require? This problem could be posed in terms of what APIs for program analysis results do you expect? | |'Program analysis can be both challenging and require specialized expertise. What requirements do you have for program analysis and what level of expertise you expect to require? This problem could be posed in terms of what APIs for program analysis results do you expect? | ||
| Line 50: | Line 50: | ||
|(CORVETTE) | |(CORVETTE) | ||
|N/A | |N/A | ||
| | |all of the above | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
|'''What general purpose languages do you expect to use and or extend to support your research work?" | |'''What general purpose languages do you expect to use and or extend to support your research work?" | ||
| Line 62: | Line 62: | ||
|(CORVETTE) | |(CORVETTE) | ||
|N/A | |N/A | ||
|( | |PIPER components will be written in C/C++ plus scripting languages (mostly python) | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
|'''Do you expect to use, require, or develop an Embedded DSL (defined by compiler support that would leverage semantics of abstractions defined completely within a general purpose base language) or an Extended DSL (define by compiler support that would leverage semantics of abstractions defined by new syntax)?" | |'''Do you expect to use, require, or develop an Embedded DSL (defined by compiler support that would leverage semantics of abstractions defined completely within a general purpose base language) or an Extended DSL (define by compiler support that would leverage semantics of abstractions defined by new syntax)?" | ||
| Line 74: | Line 74: | ||
|(CORVETTE) | |(CORVETTE) | ||
|N/A | |N/A | ||
| | |N/A | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
|''' What generic and customized code transformations do you require to support your project?" | |''' What generic and customized code transformations do you require to support your project?" | ||
| Line 86: | Line 86: | ||
|(CORVETTE) | |(CORVETTE) | ||
|N/A | |N/A | ||
| | |Instrumentation | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
|'''Which level of Intermediate Representation do you prefer to work with: source level, normalized middle level, or low level (close to binary code)? " | |'''Which level of Intermediate Representation do you prefer to work with: source level, normalized middle level, or low level (close to binary code)? " | ||
| Line 98: | Line 98: | ||
|(CORVETTE) | |(CORVETTE) | ||
|N/A | |N/A | ||
| | |N/A | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
|'''Which parallel programming models (MPI, OpenMP, UPC, etc.) do you want to have better compiler support? " | |'''Which parallel programming models (MPI, OpenMP, UPC, etc.) do you want to have better compiler support? " | ||
| Line 110: | Line 110: | ||
|(CORVETTE) | |(CORVETTE) | ||
|N/A | |N/A | ||
| | |N/A | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
|'''What OS configuration and hardware platforms do you want to run the compiler? " | |'''What OS configuration and hardware platforms do you want to run the compiler? " | ||
| Line 122: | Line 122: | ||
|(CORVETTE) | |(CORVETTE) | ||
|N/A | |N/A | ||
| | |N/A | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
|'''How do you expect compilers to incorporate domain-specific information, through DSL, separated semantics-specification files, or other methods? " | |'''How do you expect compilers to incorporate domain-specific information, through DSL, separated semantics-specification files, or other methods? " | ||
| Line 134: | Line 134: | ||
|(CORVETTE) | |(CORVETTE) | ||
|N/A | |N/A | ||
| | |N/A | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
|'''How do you expect compilers to interact with your libraries or runtime systems, if any ? " | |'''How do you expect compilers to interact with your libraries or runtime systems, if any ? " | ||
| Line 146: | Line 146: | ||
|(CORVETTE) | |(CORVETTE) | ||
|N/A | |N/A | ||
| | |Yes: by providing additional debug/code to abstraction mapping information | ||
|} | |} | ||
Revision as of 05:40, May 1, 2014
Sonia requested that Dan Quinlan initiate this page. For comments, please contact Dan Quinlan. This page is still in development.
| QUESTIONS | XPRESS | TG X-Stack | DEGAS | D-TEC | DynAX | X-TUNE | GVR | CORVETTE | SLEEC | PIPER |
|---|---|---|---|---|---|---|---|---|---|---|
| PI | Ron Brightwell | Shekhar Borkar | Katherine Yelick | Daniel Quinlan | Guang Gao | Mary Hall | Andrew Chien | Koushik Sen | Milind Kulkarni | Martin Schulz |
| Describe how you expect to require compiler support within your X-Stack project. | (EXPRESS) | (TG) | (DEGAS) | (D-TEC) | (DynAX) | (X-TUNE) | (GVR) | (CORVETTE) | SLEEC | PIPER does not have/need its own compiler, but we need access to compiler generated information that captures high-level semantics of the language implemented (basically a form of DWARF for DSLs). Additionally, advanced instrumentation or instrumentation point/markers could be useful. |
| 'Program analysis can be both challenging and require specialized expertise. What requirements do you have for program analysis and what level of expertise you expect to require? This problem could be posed in terms of what APIs for program analysis results do you expect? | (EXPRESS) | (TG) | (DEGAS) | (D-TEC) | (DynAX) | (X-TUNE) | (GVR) | (CORVETTE) | N/A | (PIPER) |
| What types of hardware do you expect to address/target within optimizations and at what level of granularity of the program (e.g. coarse-grain, over multiple functions, or fine-grain within statements)? | (EXPRESS) | (TG) | (DEGAS) | (D-TEC) | (DynAX) | (X-TUNE) | (GVR) | (CORVETTE) | N/A | all of the above |
| What general purpose languages do you expect to use and or extend to support your research work?" | (EXPRESS) | (TG) | (DEGAS) | (D-TEC) | (DynAX) | (X-TUNE) | (GVR) | (CORVETTE) | N/A | PIPER components will be written in C/C++ plus scripting languages (mostly python) |
| Do you expect to use, require, or develop an Embedded DSL (defined by compiler support that would leverage semantics of abstractions defined completely within a general purpose base language) or an Extended DSL (define by compiler support that would leverage semantics of abstractions defined by new syntax)?" | (EXPRESS) | (TG) | (DEGAS) | (D-TEC) | (DynAX) | (X-TUNE) | (GVR) | (CORVETTE) | N/A | N/A |
| What generic and customized code transformations do you require to support your project?" | (EXPRESS) | (TG) | (DEGAS) | (D-TEC) | (DynAX) | (X-TUNE) | (GVR) | (CORVETTE) | N/A | Instrumentation |
| Which level of Intermediate Representation do you prefer to work with: source level, normalized middle level, or low level (close to binary code)? " | (EXPRESS) | (TG) | (DEGAS) | (D-TEC) | (DynAX) | (X-TUNE) | (GVR) | (CORVETTE) | N/A | N/A |
| Which parallel programming models (MPI, OpenMP, UPC, etc.) do you want to have better compiler support? " | (EXPRESS) | (TG) | (DEGAS) | (D-TEC) | (DynAX) | (X-TUNE) | (GVR) | (CORVETTE) | N/A | N/A |
| What OS configuration and hardware platforms do you want to run the compiler? " | (EXPRESS) | (TG) | (DEGAS) | (D-TEC) | (DynAX) | (X-TUNE) | (GVR) | (CORVETTE) | N/A | N/A |
| How do you expect compilers to incorporate domain-specific information, through DSL, separated semantics-specification files, or other methods? " | (EXPRESS) | (TG) | (DEGAS) | (D-TEC) | (DynAX) | (X-TUNE) | (GVR) | (CORVETTE) | N/A | N/A |
| How do you expect compilers to interact with your libraries or runtime systems, if any ? " | (EXPRESS) | (TG) | (DEGAS) | (D-TEC) | (DynAX) | (X-TUNE) | (GVR) | (CORVETTE) | N/A | Yes: by providing additional debug/code to abstraction mapping information |