similar to: [LLVMdev] any option can control final linker choice in LLVM?

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 ��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

Hi , I am new to llvm.I met a problem with the jit debug. According to DebuggingJITedCode.html ,I do the same step of this document. But my gdb can't get the symbol. When i did the same thing on linux ,the result is correct. But on windows, i failed. Why? I build the llvm with vc2008, os winxp.

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, 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

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.

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

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

On Tue, Nov 1, 2011 at 18:24, Tang Luba <lubatang at gmail.com> wrote: > In GCC, LTO causes 'fat' object files, because GCC needs to serialize > IR into 'intermediate language' (IL) and compress IL in object files. > In our experience, the 'fat' object files are x10 bigger than the > original one, and slow down the linking process significantly. The >

Hi all, The slides we used on "CGO MCLinker and LLVM Tutorial" are now available on the MCLinker website: http://code.google.com/p/mclinker/wiki/2013CGOTutorial Enjoy! - The CGO Tutorial on MCLinker and LLVM 2013 committee

Hi, Brooks, Since this project is helped by many BSD guys in Taiwan, one of MCLinker's main objectives is make direct contribution to the BSD realm. Please feel free to give us suggestions to make sure we can achieve this goal. Any comments are appreciated. We realized open discussion on the mailing list is necessary, and we hope this thread can be a beginning to openly discuss the project

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

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

> 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 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 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

> 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,

Hi all, I have some troubles in writing XXInstFormat.td for my little backend. I don't know how should I start writing up this file. Is there any general rule? 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: http://people.cs.nctu.edu.tw/~chenwj

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