similar to: [LLVMdev] a problem of jit debug

Hi, Tang > result is correct. But on windows, i failed. Why? I build the llvm > with vc2008, os winxp. At the end of http://llvm.org/docs/DebuggingJITedCode.html, it said, "At the time of this writing, LLVM only supports architectures that use ELF object files and it only generates symbols and DWARF CFA information." Maybe this is the reason why you read nothing on Windows.

hi ��f�� but in the source code i find this comment. // ELF is a reasonably sane default and the only other X86 targets we // support are Darwin and Windows. Just use "not those". does this means that we can debug jit on windows? i am confused.help 2011/6/7 ��f�� <chenwj at iis.sinica.edu.tw>: > Hi, Tang > >> result is correct. But on windows, i failed. Why? I build

the reason I built llvm with vc is that I am familiar with vc. At first i also thing that build llvm with MingW will solve this problem. but after I read the source code void JITDebugRegisterer::RegisterFunction(const Function *F, DebugInfo &I) { // TODO: Support non-ELF platforms. if (!TM.getELFWriterInfo()) return; ...... } I thing MinGW is helpless with debug jit on win.

Hi All, I want to build cross compiler with LLVM-3.2 for X86, and hope LLVM compiler driver to pick up linker located in cross toolchain directory. It seems LLVM driver always chooses system linker "/usr/bin/ld" by default. Any option can be used to control? Thanks in advance! wei -------------- next part -------------- An HTML attachment was scrubbed... URL:

On Tue, Feb 26, 2013 at 11:24:39PM +0800, Wei Tang wrote: > Hi All, >     I want to build cross compiler with LLVM-3.2 for X86, and hope LLVM > compiler driver to pick up linker located > in cross toolchain directory. It seems LLVM driver always chooses system linker > "/usr/bin/ld" by default.  > Any option can be used to control?  Thanks in advance! I remember

Hi, Tang > but in the source code i find this comment. > // ELF is a reasonably sane default and the only other X86 targets we > // support are Darwin and Windows. Just use "not those". I guess you found above comment in lib/Target/X86/X86Subtarget.h. But I think X86Subtarget.h is only related to the codegen, but NOT the debugging information. The comment means you can

I'm trying to build the sources from the svn trunk using VC2008, and I'm running into some problems. First, I have no idea what the configure project is for, and it fails with a manifest related error (the project lacks any .c* files anyway). This causes an avalanche of problems, initiated by TableGen not being able to build. Has anyone been successful in getting the LLVM libs to build

Hello, I'm interested in debugging code JITted by LLVM at runtime. For that, I should naturally have some way to emit DWARF that faithfully describes the JITted code into memory along with the JITted code itself and point the debugger to it. Let's assume that the bridge with the debugger is taken care of (e.g. http://llvm.org/docs/DebuggingJITedCode.html) - my concern in this question is

so as you said , there is no hop for debug jit on windows? 2011/6/7 ��f�� <chenwj at iis.sinica.edu.tw>: > Hi, Tang > >> but in the source code i find this comment. >> // ELF is a reasonably sane default and the only other X86 targets we >> // support are Darwin and Windows. Just use "not those". > > I guess you found above comment in

Dear LLVM user and developer, We get a chance to give a tutorial on LLVM and MCLinker. The tutorial will be co-located with CGO 2013 on Feb. 24 (Sunday morning) in Shenzhen, China. If you are also interesting in these topics, welcome to join the tutorial! Here is a website of the tutorial: http://code.google.com/p/mclinker/ We're also looking for additional presenters to share a

Hi, I’m wondering if it’s possible to debug code JIT’ed with the newer ORC JIT. The LLVM documentation has a page at llvm.org/docs/DebuggingJITedCode.html <http://llvm.org/docs/DebuggingJITedCode.html> showing an example of using gdb to debug MCJIT’ed code, but has no mention of ORC JIT. From searching around online I’ve gotten the impression that ORC JIT does *not* support providing

Hi Justin, I believe the PTX section in the link below need some love, updating "lib/Target/PTX" to "lib/Target/NVPTX" for example. Would you like to take a look? http://llvm.org/docs/CodeGenerator.html#the-ptx-backend Regards, chenwj -- Wei-Ren Chen (陳韋任) Computer Systems Lab, Institute of Information Science, Academia Sinica, Taiwan (R.O.C.) Tel:886-2-2788-3799 #1667

> In consideration of those codes in XXXAsmPrinter class which print out > MachineInstr in .s format, I tend to think they are old codes that > might be obsolete and will be replaced with MC layer implementation, > but I am not sure. How about sending a patch which remove those obsolete code, and let others give comment? Cheers, chenwj -- Wei-Ren Chen (陳韋任) Computer Systems Lab,

Hi all, I think it's Gentoo's bug, but I want to know if anyone has the same issue here. I am compiling LLVM trunk on Gentoo (gcc 4.5.2), and I get error message below, --- make[4]: Entering directory `/nfs_home/chenwj/llvm-3.1/svn/build/tools/clang/lib/Frontend' llvm[4]: Compiling InitHeaderSearch.cpp for Release+Asserts build

On Mon, Nov 07, 2011 at 04:10:29PM +0100, Wim Vander Schelden wrote: > I'm having the same problem. Does anyone know what's causing this? > > Kind regards, > > Wim What's your profiling procedure? I can only guess llvm-prof does not recognize the profiling data. Regards, chenwj -- Wei-Ren Chen (陳韋任) Computer Systems Lab, Institute of Information Science, Academia

Thx all for the quick answers... > De : llvmdev-bounces at cs.uiuc.edu [llvmdev-bounces at cs.uiuc.edu] de la part de Arnaud ALLARD DE GRANDMAISON [arnaud.allarddegrandmaison at parrot.com] > > Hi, > > Depending on what have run before your pass, the loop may have been unrolled or simplified if the computation inside the loop is too simple. > > Cheers, > -- > Arnaud de

Hi Pawel, PTX already be replaced with NVPTX. However, PTX subdirectory still sit in lib/Target in 3.2 release. Do you think update the release tarball is a good idea? Also could you remove it from the trunk? Thanks. Regards, chenwj -- Wei-Ren Chen (陳韋任) Computer Systems Lab, Institute of Information Science, Academia Sinica, Taiwan (R.O.C.) Tel:886-2-2788-3799 #1667 Homepage:

Hi all, While building/testing LLVM/Clang on ARM, I often have problems that are undocumented on the website. I would like to contribute my experience if possible so that others can benefit from it. If this is a good idea, I am wondering on what page I should write it down, [1] or [2]? Regards, chenwj [1] http://llvm.org/docs/GettingStarted.html [2] http://llvm.org/docs/FAQ.html -- Wei-Ren

On 24 April 2011 00:57, 陳韋任 <chenwj at iis.sinica.edu.tw> wrote: > Hi, Zhao > > You can apply the attachment to LLVM 2.9 Release. It has been tested > on FreeBSD/x86. > Hi Chen, may I commit this (updated to include GCDAProfiling.cpp) to LLVM SVN? Nick > > Regards, > chenwj > > -- > Wei-Ren Chen (陳韋任) > Computer Systems Lab, Institute of Information

> still a question: > what does "; PR1028" means? I believe it means this test case addresses bug report (pr, problem report) 1028 [1]. In other words, this test case guarantee that pr1028 will not back again. If so, it will fail. Regards, chenwj [1] http://llvm.org/bugs/show_bug.cgi?id=1028 -- Wei-Ren Chen (陳韋任) Computer Systems Lab, Institute of Information Science,