search for: ccxx

Hi, i'm not new with wine but i'm in trouble with an old vb application. I just tried everything i know to solve but i'm still at the start point. I want to open a document (.rtf or .doc ) with OO . This VB application needs the full path of the application i want to use to open the documents. I write down the complete and full path ( Z:/xxx/yy/oowriter ). The path is correct and the

The debug information is actually still in a different format in the .bc file, it is LLVM metadata. I think the best reference for it is here: https://llvm.org/docs/SourceLevelDebugging.html#ccxx-frontend You can dump it just by disassembling the .bc file to textual IR using llvm-dis and examining the !DI* metadata nodes. You will have to run the file through llc to generate an object file to generate actual CodeView or DWARF. On Wed, Jan 17, 2018 at 5:09 AM, 陳韋任 via llvm-dev <llvm-dev...

...org> Date: 17.01.2018 18:29 Subject: Re: [llvm-dev] Dumping debug information from BC files The debug information is actually still in a different format in the .bc file, it is LLVM metadata. I think the best reference for it is here: https://llvm.org/docs/SourceLevelDebugging.html#ccxx-frontend You can dump it just by disassembling the .bc file to textual IR using llvm-dis and examining the !DI* metadata nodes. You will have to run the file through llc to generate an object file to generate actual CodeView or DWARF. On Wed, Jan 17, 2018 at 5:09 AM, 陳韋任 via llvm-dev < llvm...

> > 3.) Then I used clang-cl to generate a .bc file - but now I'm not able to > use "llvm-readobj" anymore. Is there any tool available which can dump this > debug information too? > ​.bc is LLVM bitcode [1], not the usual object file. `llvm-readobj` should works only on the latter. ​[1] https://llvm.org/docs/BitCodeFormat.html -- Wei-Ren Chen (陳韋任) Homepage:

Hello LLVM-World, I have a question about dumping debug information. 1.) I have compiled an object file with visual studio and debug information. Then I used "llvm-readobj -codeview" and dumped the debug information into a file. This is working great 2.) I used clang-cl for the same task and finally dumped it again with "llvm-readobj". Worked great too. 3.) Then I used