Difference between revisions of "CC 2007"
Jump to navigation
Jump to search
(Created page with "{{Event |Acronym=CC 2007 |Title=International Conference on Compiler Construction |Ordinal=16 |Series=CC |Type=Conference |Start date=2007/03/26 |End date=2007/03/30 |Submissi...") |
Tim Holzheim (talk | contribs) (Added page provenance(#264) and contribution type(#271)) |
||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{Event | {{Event | ||
| − | | | + | |Superevent=ETAPS 2007 |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|Submission deadline=2006/10/13 | |Submission deadline=2006/10/13 | ||
| − | | | + | |gndId=6063720-1 |
| − | |||
| − | |||
| − | |||
|Notification=2006/12/08 | |Notification=2006/12/08 | ||
|Camera ready=2007/01/05 | |Camera ready=2007/01/05 | ||
|has program chair=Shriram Krishnamurthi, Martin Odersky | |has program chair=Shriram Krishnamurthi, Martin Odersky | ||
|has Keynote speaker=Don Batory | |has Keynote speaker=Don Batory | ||
| + | |has Proceedings DOI=https://doi.org/10.1007/978-3-540-71229-9 | ||
| + | |has Proceedings Bibliography=https://link.springer.com/book/10.1007%2F978-3-540-71229-9 | ||
| + | |Acronym =CC 2007 | ||
| + | |End date=2007-03-30 | ||
| + | |Series =CC | ||
| + | |presence=presence | ||
| + | |Type =Conference | ||
| + | |Country =BR | ||
| + | |State =BR/RS | ||
| + | |City =BR/RS/Braga | ||
| + | |Year =2007 | ||
| + | |Homepage=https://cc2007.cs.brown.edu/ | ||
| + | |Ordinal =16 | ||
| + | |Start date=2007-03-26 | ||
| + | |Title =International Conference on Compiler Construction | ||
| + | |Accepted papers=14 | ||
| + | |Submitted papers=60 | ||
| + | |DblpConferenceId=cc/cc2007 | ||
| + | |TibKatId=537716750 | ||
| + | |wikidataid=Q106426940 | ||
| + | |pageCreator=Tolga.karaarslan | ||
| + | |pageEditor=Tolga.karaarslan|contributionType=1 | ||
}} | }} | ||
The 16. International Conference on Compiler Construction (CC) 2007 | The 16. International Conference on Compiler Construction (CC) 2007 | ||
| Line 21: | Line 34: | ||
==Topics== | ==Topics== | ||
| − | compilation and interpretation techniques, including program representation and analysis, code generation and code optimization | + | *compilation and interpretation techniques, including program representation and analysis, code generation and code optimization |
| − | run-time techniques, including memory management and dynamic and just-in-time compilation | + | *run-time techniques, including memory management and dynamic and just-in-time compilation |
| − | programming tools, from refactoring editors to checkers to compilers to virtual machines to debuggers | + | *programming tools, from refactoring editors to checkers to compilers to virtual machines to debuggers |
| − | techniques for specific domains, such as secure, parallel, distributed, embedded or mobile environments | + | *techniques for specific domains, such as secure, parallel, distributed, embedded or mobile environments |
| − | design of novel language constructs and their implementation | + | *design of novel language constructs and their implementation |
| Line 31: | Line 44: | ||
CC accepts both research papers and tool demonstration papers. Research papers cover one or more of the topics above, including reports on tool development and case studies that focus on scientific contributions. All such papers should clearly state the problem under study, propose a solution, and evaluate the solution. Tool demonstration papers focus on novel and useful tools. Both types of contributions will appear in the proceedings and have oral presentations during the conference. Both will be evaluated by the CC Program Committee. | CC accepts both research papers and tool demonstration papers. Research papers cover one or more of the topics above, including reports on tool development and case studies that focus on scientific contributions. All such papers should clearly state the problem under study, propose a solution, and evaluate the solution. Tool demonstration papers focus on novel and useful tools. Both types of contributions will appear in the proceedings and have oral presentations during the conference. Both will be evaluated by the CC Program Committee. | ||
| − | All papers must | + | All papers must:<br> |
| − | + | *be in English | |
| − | be in English | + | *present original work that is unpublished and has not submitted elsewhere (conferences or journals), including other ETAPS venues |
| − | present original work that is unpublished and has not submitted elsewhere (conferences or journals), including other ETAPS venues | + | *be prepared using the Springer-Verlag LNCS style |
| − | be prepared using the Springer-Verlag LNCS style | + | *come in PDF format viewable and printable by Acrobat Reader |
| − | come in PDF format viewable and printable by Acrobat Reader | + | *be submitted in full by the date given below |
| − | be submitted in full by the date given below | + | *Research papers can use a maximum of 15 (fifteen) pages, including figures, bibliography, and appendices. |
| − | Research papers can use a maximum of 15 (fifteen) pages, including figures, bibliography, and appendices. | ||
| − | |||
| − | The first part, at most 4 (four) pages, should describe the tool. Please include the URL of the tool (if available) and provide information that illustrates the maturity and robustness of the tool. (This part will be included in the proceedings.) | + | Tool Demonstration papers must consist of two parts:<br> |
| − | The second part, at most 6 (six) pages, should explain how the demonstration will be carried out and what it will show, including screen dumps and examples. (This part will be not be included in the proceedings, but will be evaluated for acceptance.) | + | *The first part, at most 4 (four) pages, should describe the tool. Please include the URL of the tool (if available) and provide information that illustrates the maturity and robustness of the tool. (This part will be included in the proceedings.) |
| + | *The second part, at most 6 (six) pages, should explain how the demonstration will be carried out and what it will show, including screen dumps and examples. (This part will be not be included in the proceedings, but will be evaluated for acceptance.) | ||
Submissions that deviate from these parameters will be rejected without review. | Submissions that deviate from these parameters will be rejected without review. | ||
==Important Dates== | ==Important Dates== | ||
| − | Submissions due: October 13, 2006 | + | Submissions due: October 13, 2006<br> |
| − | Acceptance notification: December 8, 2006 | + | Acceptance notification: December 8, 2006<br> |
| − | Camera-ready papers due: January 5, 2007 | + | Camera-ready papers due: January 5, 2007<br> |
CC conference: TBD (between March 26 and 30, 2007) | CC conference: TBD (between March 26 and 30, 2007) | ||
Latest revision as of 20:23, 1 April 2022
| CC 2007 | |
|---|---|
International Conference on Compiler Construction
| |
| Ordinal | 16 |
| Event in series | CC |
| Subevent of | ETAPS 2007 |
| Dates | 2007-03-26 (iCal) - 2007-03-30 |
| Presence | presence |
| Homepage: | https://cc2007.cs.brown.edu/ |
| Location | |
| Location: | BR/RS/Braga, BR/RS, BR |
| Important dates | |
| Submissions: | 2006/10/13 |
| Notification: | 2006/12/08 |
| Camera ready due: | 2007/01/05 |
| Papers: | Submitted 60 / Accepted 14 (23.3 %) |
| Committees | |
| PC chairs: | Shriram Krishnamurthi, Martin Odersky |
| Keynote speaker: | Don Batory |
| Table of Contents | |
The following coordinate was not recognized: Geocoding failed.The following coordinate was not recognized: Geocoding failed.
The 16. International Conference on Compiler Construction (CC) 2007
Topics
- compilation and interpretation techniques, including program representation and analysis, code generation and code optimization
- run-time techniques, including memory management and dynamic and just-in-time compilation
- programming tools, from refactoring editors to checkers to compilers to virtual machines to debuggers
- techniques for specific domains, such as secure, parallel, distributed, embedded or mobile environments
- design of novel language constructs and their implementation
Submissions
CC accepts both research papers and tool demonstration papers. Research papers cover one or more of the topics above, including reports on tool development and case studies that focus on scientific contributions. All such papers should clearly state the problem under study, propose a solution, and evaluate the solution. Tool demonstration papers focus on novel and useful tools. Both types of contributions will appear in the proceedings and have oral presentations during the conference. Both will be evaluated by the CC Program Committee.
All papers must:
- be in English
- present original work that is unpublished and has not submitted elsewhere (conferences or journals), including other ETAPS venues
- be prepared using the Springer-Verlag LNCS style
- come in PDF format viewable and printable by Acrobat Reader
- be submitted in full by the date given below
- Research papers can use a maximum of 15 (fifteen) pages, including figures, bibliography, and appendices.
Tool Demonstration papers must consist of two parts:
- The first part, at most 4 (four) pages, should describe the tool. Please include the URL of the tool (if available) and provide information that illustrates the maturity and robustness of the tool. (This part will be included in the proceedings.)
- The second part, at most 6 (six) pages, should explain how the demonstration will be carried out and what it will show, including screen dumps and examples. (This part will be not be included in the proceedings, but will be evaluated for acceptance.)
Submissions that deviate from these parameters will be rejected without review.
Important Dates
Submissions due: October 13, 2006
Acceptance notification: December 8, 2006
Camera-ready papers due: January 5, 2007
CC conference: TBD (between March 26 and 30, 2007)