[llvm-bugs] [Bug 43757] New: Debug Info should have no effect on codegen

via llvm-bugs llvm-bugs at lists.llvm.org
Mon Oct 21 21:06:15 PDT 2019


            Bug ID: 43757
           Summary: Debug Info should have no effect on codegen
           Product: clang
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: LLVM Codegen
          Assignee: unassignedclangbugs at nondot.org
          Reporter: yechunliangcn at 163.com
                CC: llvm-bugs at lists.llvm.org, neeilans at live.com,
                    richard-llvm at metafoo.co.uk

This bug is a summary for bugs will be reported related with "Debug Info should
have no effect on codegen" - the project of the Google Summer of Code 2019 (ref
to http://llvm.org/OpenProjects.html#debuginfo_codegen_mismatch)

Description of the project: Adding Debug Info (compiling with `clang -g`)
shouldn't change the generated code at all. Unfortunately we have bugs. These
are usually not too hard to fix and a good way to discover new part of the
codebase! We suggest building object files both ways and disassembling the text
sections, which will give cleaner diffs than comparing .s files.

Expected results: Reduced test cases, bug reports with analysis (e.g., which
pass is responsible), possibly patches.

Proposed ways to find a bug:
    1. "with/without -g": Using check_cfc.py to scan code on llvm_test_suite
project. (Several bugs already found and will report out)
    2. "with/without -strip-debug": using opt command to scan code on
llvm/test/*.ll (not try yet, assume there have bugs)

You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20191022/7c2d5d46/attachment.html>

More information about the llvm-bugs mailing list