[cfe-dev] Scan, Parse, IR Codegen & Debug compatibility
Allyn Shell via cfe-dev
cfe-dev at lists.llvm.org
Fri May 22 12:51:11 PDT 2020
From: David Blaikie <dblaikie at gmail.com>
Sent: Thursday, May 21, 2020 5:54 PM
To: Allyn Shell <ashell2 at jhu.edu>
Cc: via cfe-dev <cfe-dev at lists.llvm.org>
Subject: Re: [cfe-dev] Scan, Parse, IR Codegen, Debug
Is the transition between AST and IR mapped in a way that is compatible with the mappings used for debug and the IR to Machine Specific Object Code?
I'm not sure I understand the question, could you rephrase it? Myself and Eric Christopher presented a tutorial at the LLVM developers meeting several years ago about how to generate LLVM IR that includes debug information that is then used by LLVM's middle (IR optimizations) and backend (Machine Specific Object Code generation) to create DWARF (or Windows CodeView) debug information, usable by a debugger like gdb, etc.
AMS: I appologize for not having a reference, but while I was reading all the LLVM documentation, I read that TableGen and the DWARD debug format had mappings that somebody recomended be made consistent with the target independent code generation so that there would only be one mapping for these things instead of different mappings at the different levels. I simply wanted to know if that effort toward uniformity was being advanced and if the AST to IR code generation was planned to be part of the uniformity. (And if not, should I consider trying to be compatible with some ongoing effort to create uniformity of mappings across phases of LLVM while I add front end features.)
Where can I find that information?
The written version of that tutorial is here: https://llvm.org/docs/tutorial/MyFirstLanguageFrontend/LangImpl09.html
cfe-dev mailing list
cfe-dev at lists.llvm.org<mailto:cfe-dev at lists.llvm.org>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the cfe-dev