<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">I think an easy way to start here would probably be to use the test suite, or a subset of it.<div class=""><br class=""></div><div class="">I would recommend using the SingleSource tests to start out with. The MultiSource tests will lead you into having to bisect on object files, which is a bit more work. There are a couple of large SingleSource tests which I imagine might have a few differences in them.<div class=""><div class=""><br class=""></div><div class="">A workflow like this might help you get started with finding examples of different codegen:</div><div class=""><br class=""></div><div class="">1) Build, but don’t execute, the tests with debug info</div><div class="">2) Build, but don’t execute, the tests without debug info</div><div class="">3) Use test-suite/utils/compare.py on the output JSON reports to check if there are any differences in, say, text size (which implies different codegen)</div><div class="">4) Bisect on object files if necessary </div><div class="">5) Use something like bugpoint to reduce the testcase</div><div class=""><br class=""></div><div class="">You can build the LLVM test suite by following the instructions here:</div><div class=""><a href="http://llvm.org/docs/lnt/quickstart.html" class="">http://llvm.org/docs/lnt/quickstart.html</a></div><div class=""><br class=""></div><div class="">I find this blog post pretty useful for bugpoint stuff:</div><div class=""><a href="http://blog.llvm.org/2015/11/reduce-your-testcases-with-bugpoint-and.html" class="">http://blog.llvm.org/2015/11/reduce-your-testcases-with-bugpoint-and.html</a></div><div class=""><br class=""></div><div class="">- Jessica</div><div class=""><br class=""></div><div class=""><div class=""><div class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Mar 5, 2019, at 7:54 AM, Mohamed Ali via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div dir="ltr" class="">Dear all,<div class=""><br class=""></div><div class="">My name is Mohamed and I am a first year computer science masters student. I am writing this email because I am interested in the project idea "Debug Info Should have no effect on codegen". So far I have built llvm and clang and I was trying to reproduce the problem on simple c++ programs but I can't. Being specific this are the steps I am doing:</div><div class=""><br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">$ clang -g <a href="http://test.cc" class="">test.cc</a><br class="">$ llvm-objdump -d a.out > with_debug<br class="">$ clang <a href="http://test.cc" class="">test.cc</a><br class="">$ llvm-objdump -d a.out > no_debug<br class="">$ vimdiff with_debug no_debug</blockquote><div class=""> </div><div class="">I still can't reproduce the problem. In the expected results of the project you mentioned that there are already failing test cases. Can you please point me in to these cases?</div><div class="">Finally, I would like to ask whether there is some qualification task I should do or I have to fix some of the open tickets? Would you please point me to such tasks or suggest some tickets/bugs that I can start working on?</div><div class=""><br class=""></div><div class="">Regards,</div><div class="">Mohamed</div></div></div>
_______________________________________________<br class="">LLVM Developers mailing list<br class=""><a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a><br class="">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev<br class=""></div></blockquote></div><br class=""></div></div></div></div></div></body></html>