BTW, that's the exact approach I took for fixing Rust's debug info emitter.
On Wed, May 29, 2013 at 2:00 PM, Wojciech Matyjewicz < [email protected]> wrote: > On 29.05.2013 17:01, Michael Wörister wrote: > >> Hi everyone, >> I wanted to quickly introduce myself here. My name is Michael Woerister >> and I was accepted for Rust's Google Summer of Code project this year, >> regarding debug symbol generation for rustc. >> > > Congratulations and good luck! > > As for comments (please, excuse me if I am writing something obvious): I > have noticed that the current implementation in debuginfo.rs emits debug > information by directly building proper LLVM metadata nodes using the > low-level functions. An alternative approach could be taken by using LLVM's > DIBuilder [1] class that abstracts these low-level functions and the > debugging metadata format into a higher-level interface. Taking this > approach would involve creating bindings for DIBuilder. However, this > effort might pay off in the longer term, because all the (undocumented) > changes that may happen to the LLVM's low-level debug information format > would be hidden behind DIBuilder. The other benefit is that DIBuilder keeps > track of what metadata nodes it has generated and reuses the existing nodes > instead of generating identical ones --- similar functionality from > debuginfo.rs could be removed then. > > Cheers, > Wojtek > ______________________________**_________________ > Rust-dev mailing list > [email protected] > https://mail.mozilla.org/**listinfo/rust-dev<https://mail.mozilla.org/listinfo/rust-dev> >
_______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
