search for: zmlt

...th debug info at the > same time, but it's a readonly format at debug emission so I don't see > it as being a problem. Well, if two debug formats share the same section name, they might conflict with each other. I don't think this is the case for Dwarf&CodeView [yet?]. > -Zmlt makes sense as the clang-cl name, or just > make it whatever the debug mode flag is for cl.exe - this is at least > a start down that path. 2013/11/19 Reid Kleckner <rnk at google.com>: > I'd just use /Z7, since that's the cl.exe flag for the compatible format. > This wil...

...option to code gen maybe or, for now, make it dependent upon triple. The former is, I think, the best option there. I'm not sure if you're going to want to support both debug info at the same time, but it's a readonly format at debug emission so I don't see it as being a problem. -Zmlt makes sense as the clang-cl name, or just make it whatever the debug mode flag is for cl.exe - this is at least a start down that path. I think the best way for the tests will be to write a set of parsers, etc that can dump the info. I realize this is likely a very large undertaking as well, but i...

...hat's the cl.exe flag for the compatible format. > > This will need a long-form clang -cc1 flag name, though. > > Z7 implies a much more complete debug info than what we'll emit short-term. > Since Z7 is not widely used, I don't think threading Z7 is any simpler > than Zmlt. > I don't have a strong opinion though, WDYT? My thinking is that it works well with /fallback. We'll make Z7-style debug info, and for TUs compiled with cl.exe, we'll get the same style info. -------------- next part -------------- An HTML attachment was scrubbed... URL: <htt...

...t at debug emission so I don't see > >> it as being a problem. > > > > Well, if two debug formats share the same section name, they might > > conflict with each other. > > I don't think this is the case for Dwarf&CodeView [yet?]. > > > >> -Zmlt makes sense as the clang-cl name, or just > >> make it whatever the debug mode flag is for cl.exe - this is at least > >> a start down that path. > > > > 2013/11/19 Reid Kleckner <rnk at google.com>: > >> I'd just use /Z7, since that's the cl.exe...

...> questions and suggestions. >> > >> > Some general questions: >> > 1) Threading flags from the driver down to CodeGen. >> > How do we do that? Should we support all 4 combinations >> > of no-info/DWARF/CVLT/both? >> > How about "-Zmlt" as the clang-cl flag name? ("minimal line tables") >> > >> > 2) Am I right that DWARF is pretty much the only debug info format >> > supported by LLVM/AsmPrinter right now? Do we want to take >> > an effort to come up with a generic debuginfo...

...time, but it's a readonly format at debug emission so I don't see >> it as being a problem. > > Well, if two debug formats share the same section name, they might > conflict with each other. > I don't think this is the case for Dwarf&CodeView [yet?]. > >> -Zmlt makes sense as the clang-cl name, or just >> make it whatever the debug mode flag is for cl.exe - this is at least >> a start down that path. > > 2013/11/19 Reid Kleckner <rnk at google.com>: >> I'd just use /Z7, since that's the cl.exe flag for the compatible...

...ut a few TODOs with > > questions and suggestions. > > > > Some general questions: > > 1) Threading flags from the driver down to CodeGen. > > How do we do that? Should we support all 4 combinations > > of no-info/DWARF/CVLT/both? > > How about "-Zmlt" as the clang-cl flag name? ("minimal line tables") > > > > 2) Am I right that DWARF is pretty much the only debug info format > > supported by LLVM/AsmPrinter right now? Do we want to take > > an effort to come up with a generic debuginfogenerator interf...

...pretty sure I made a few weird things in the code... I've also put a few TODOs with questions and suggestions. Some general questions: 1) Threading flags from the driver down to CodeGen. How do we do that? Should we support all 4 combinations of no-info/DWARF/CVLT/both? How about "-Zmlt" as the clang-cl flag name? ("minimal line tables") 2) Am I right that DWARF is pretty much the only debug info format supported by LLVM/AsmPrinter right now? Do we want to take an effort to come up with a generic debuginfogenerator interface to share between DwarfDebug and W...

...'t see >> >> it as being a problem. >> > >> > Well, if two debug formats share the same section name, they might >> > conflict with each other. >> > I don't think this is the case for Dwarf&CodeView [yet?]. >> > >> >> -Zmlt makes sense as the clang-cl name, or just >> >> make it whatever the debug mode flag is for cl.exe - this is at least >> >> a start down that path. >> > >> > 2013/11/19 Reid Kleckner <rnk at google.com>: >> >> I'd just use /Z7, since t...

...ngs in the code... I've also put a few TODOs with > questions and suggestions. > > Some general questions: > 1) Threading flags from the driver down to CodeGen. > How do we do that? Should we support all 4 combinations > of no-info/DWARF/CVLT/both? > How about "-Zmlt" as the clang-cl flag name? ("minimal line tables") > > 2) Am I right that DWARF is pretty much the only debug info format > supported by LLVM/AsmPrinter right now? Do we want to take > an effort to come up with a generic debuginfogenerator interface > to share...

...t;>>>> > 1) Threading flags from the driver down to CodeGen. >> >>>>>> > How do we do that? Should we support all 4 combinations >> >>>>>> > of no-info/DWARF/CVLT/both? >> >>>>>> > How about "-Zmlt" as the clang-cl flag name? ("minimal line >> >>>>>> > tables") >> >>>>>> > >> >>>>>> > 2) Am I right that DWARF is pretty much the only debug info >> >>>>>> > format >>...

...gt; > 1) Threading flags from the driver down to CodeGen. > >> >>>>>> > How do we do that? Should we support all 4 combinations > >> >>>>>> > of no-info/DWARF/CVLT/both? > >> >>>>>> > How about "-Zmlt" as the clang-cl flag name? ("minimal line > >> >>>>>> > tables") > >> >>>>>> > > >> >>>>>> > 2) Am I right that DWARF is pretty much the only debug info > >> >>>>>> &...

...Threading flags from the driver down to CodeGen. >> >> >>>>>> > How do we do that? Should we support all 4 combinations >> >> >>>>>> > of no-info/DWARF/CVLT/both? >> >> >>>>>> > How about "-Zmlt" as the clang-cl flag name? ("minimal line >> >> >>>>>> > tables") >> >> >>>>>> > >> >> >>>>>> > 2) Am I right that DWARF is pretty much the only debug info >> >> >>&g...

...e general questions: >>>>>> > 1) Threading flags from the driver down to CodeGen. >>>>>> > How do we do that? Should we support all 4 combinations >>>>>> > of no-info/DWARF/CVLT/both? >>>>>> > How about "-Zmlt" as the clang-cl flag name? ("minimal line tables") >>>>>> > >>>>>> > 2) Am I right that DWARF is pretty much the only debug info format >>>>>> > supported by LLVM/AsmPrinter right now? Do we want to take >>>&...

...> >>>>>> > 1) Threading flags from the driver down to CodeGen. > >>>>>> > How do we do that? Should we support all 4 combinations > >>>>>> > of no-info/DWARF/CVLT/both? > >>>>>> > How about "-Zmlt" as the clang-cl flag name? ("minimal line > tables") > >>>>>> > > >>>>>> > 2) Am I right that DWARF is pretty much the only debug info format > >>>>>> > supported by LLVM/AsmPrinter right now? Do we want t...

...> questions and suggestions. >> > >> > Some general questions: >> > 1) Threading flags from the driver down to CodeGen. >> > How do we do that? Should we support all 4 combinations >> > of no-info/DWARF/CVLT/both? >> > How about "-Zmlt" as the clang-cl flag name? ("minimal line tables") >> > >> > 2) Am I right that DWARF is pretty much the only debug info format >> > supported by LLVM/AsmPrinter right now? Do we want to take >> > an effort to come up with a generic debuginfo...