Tracking issue for -Zdwarf-version · Issue #103057 · rust-lang/rust (original) (raw)

This is a tracking issue for the -Zdwarf-version unstable flag (no RFC/MCP) added in #98350 which allows selecting the specific version of DWARF to use when creating debuginfo.

About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
Discussion comments will get marked as off-topic or deleted.
Repeated discussions on the tracking issue may lead to the tracking issue getting locked.

Steps

• Initial implementation (Implement support for DWARF version 5. #98350)
• Wider Testing (tested on RfL)
• Adjust documentation (see instructions on rustc-dev-guide) (Stabilize -Zdwarf-version as -Cdwarf-version #136926)
• Stabilization PR (see instructions on rustc-dev-guide) (Stabilize -Zdwarf-version as -Cdwarf-version #136926)

Unresolved Questions

• Is the pre-compiled standard library (potentially) using a different version of DWARF an issue?
• What should the behavior of the flag do when the active target does not use DWARF?

Implementation history

• Initial implementation: Implement support for DWARF version 5. #98350
• Stop emitting .debug_pubnames and .debug_pubtypes when using DWARF 5 fix: stop emitting .debug_pubnames and .debug_pubtypes #117962
• Refactoring & cleanups Clean up uses of the unstable dwarf_version option #135739
• Fix LLVM warning on LTO with different DWARF versions Pick the max DWARF version when LTO'ing modules with different versions #136659
• Improve argument validation Emit an error if -Zdwarf-version=1 is requested #136746