(original) (raw)
Thanks, Vedant. Yes, we have done a lot of testing of Clang/LLVM (and GCC) in the past several years (more details at https://people.inf.ethz.ch/suz/emi/index.html):
\[GCC/LLVM bugs: 1,602 (total) / 1,007 (fixed)\]
\[Reports: GCC (link1, link2, link3, link4, link5), LLVM (link1, link2, link3, link4, link5)\]
\[Reports: GCC (link1, link2, link3, link4, link5), LLVM (link1, link2, link3, link4, link5)\]
Best,
Zhendong
--------
Zhendong Su
Professor, Department of Computer Science, ETH Zurich
Office: CAB E 64.1, Tel: +41 44 633 77 72
Office: CAB E 64.1, Tel: +41 44 633 77 72
--------
On Fri, Dec 7, 2018 at 7:42 PM Vedant Kumar <vsk@apple.com> wrote:
Hello,+ Zhendong, who’s done a lot of work on automated testing of llvm.On Dec 6, 2018, at 10:15 PM, Radu Ometita via llvm-dev <llvm-dev@lists.llvm.org> wrote:Hello everyone!
We are working on writing a paper about testing the reliability of C compilers by using Csmith (a random C99 program generator).
A previous testing effort, using Csmith, found 202 LLVM bugs, which represented 2% of all reported bugs at that time (PDF: https://www.flux.utah.edu/download?uid=114): . However, after this paper was published we are unaware of any further testing using Csmith, and we would like to ask you if you are aware of any such efforts or further results.Just speaking for myself here, I use Csmith as part of my pre-commit testing.vedant\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
Best regards,
Radu Ometita,
Functional compilers engineer @IOHK
LLVM Developers mailing list
llvm-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev