{"title":"编译器认证小组:我们应该信任我们的编译器吗?","authors":"Lennart Beringer, R. Brukardt, T. Plum, S. Taft","doi":"10.1145/2402676.2402708","DOIUrl":null,"url":null,"abstract":"Whether programming in a high-level modeling language providing automatic code generation, in a formally-verifiable language, in a language with advanced static analysis tools, or directly in a normal third-generation programming language, we ultimately depend on a compiler to generate the actual machine code that is executed by the target machine. This panel will discuss the issue of how we build trust in our compilers, using a commercial test suite, a standardized test suite, or a formal verification process.","PeriodicalId":402438,"journal":{"name":"HILT '12","volume":"1 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2012-11-29","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":"{\"title\":\"Panel on compiler certification: should we trust our compiler?\",\"authors\":\"Lennart Beringer, R. Brukardt, T. Plum, S. Taft\",\"doi\":\"10.1145/2402676.2402708\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"Whether programming in a high-level modeling language providing automatic code generation, in a formally-verifiable language, in a language with advanced static analysis tools, or directly in a normal third-generation programming language, we ultimately depend on a compiler to generate the actual machine code that is executed by the target machine. This panel will discuss the issue of how we build trust in our compilers, using a commercial test suite, a standardized test suite, or a formal verification process.\",\"PeriodicalId\":402438,\"journal\":{\"name\":\"HILT '12\",\"volume\":\"1 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2012-11-29\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"0\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"HILT '12\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1145/2402676.2402708\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"HILT '12","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1145/2402676.2402708","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Panel on compiler certification: should we trust our compiler?
Whether programming in a high-level modeling language providing automatic code generation, in a formally-verifiable language, in a language with advanced static analysis tools, or directly in a normal third-generation programming language, we ultimately depend on a compiler to generate the actual machine code that is executed by the target machine. This panel will discuss the issue of how we build trust in our compilers, using a commercial test suite, a standardized test suite, or a formal verification process.