similar to: [LLVMdev] LLVM-gcc for a new architecture

Boris, > Yes, I know that. configure --target=a-b-c will fail because there > is no such stuff known in gcc. So, what is the answer/consequence? An > existing gcc back-end for architecture "a" is a precondition for a > LLVM back-end for architecture "a"? No. This is requirement of using gcc as a frontend. This looks pretty weird, but it is: frontend should

Hi, I have written new dummy target to llvm-gcc for our processor architecture, which contains basically only the information which is necessary to generate llvm byte code. I could check tomorrow in work, which parts of llvm- gcc had to be altered for our "tce-llvm-gcc" cross-compiler. I also hardcoded compiler to use llvm-ld and llvm-as as it's bintools, for being able to

Jup, 64 Bit Kernel build is done now and works, but 32 Bit kernel config is different, as I use 64 Bit in Dom0 and DomU, 32 Bit only in DomU incl. DomU with DVB etc. XEN options are the same, it''s only the selection of drivers... Andrew, any idea? Boris, do you know a safe way to create a 64 Bit config out of a 32 Bit one? Sorry, I am not so used to kernel building... BR, Carsten.

Finally, I got my hands on Windows machine again today. I extracted llvm-2.1-x86-mingw32.tar.bz2 and llvm-gcc4.0-2.1-x86-mingw32.tar.bz2 to C:\llvm (It's a bare Windows Vista installation without MinGW) Added C:\llvm\bin;C:\llvm\libexec\gcc\i686-pc-mingw32\4.0.1 to PATH (C:\llvm\libexec\gcc\i686-pc-mingw32\4.0.1 was added for cc1.exe) Downloaded

Hi! This questions seems a little bit stupid, but I'll ask anyway ;-) How do I configure llvm-gcc (version 4.0.1) without having a gcc back-end, but a LLVM back-end for my new architecture? Thanks in advance, Boris

Hello, Bill. > Has anyone gotten the latest/greatest sources from the LLVM-GCC open > source server lately? No. It's still at rev 319 (as of 29.04). -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.

Hi, I have several servers Supermicro - running Xen 3.4.1 @ debian 5.0 x64 running without any issues for more than year. Now I bought new server with exactly same config and installed Ubuntu 10.04 x64 - Xen 4.0.1-rc4 - 2.6.32.16 pv_ops - base Ubuntu 10.04 install boot without issues - Xen 4.0.1-rc4 compiled and installed withou any problems - 2.6.32.16 pv_ops dom0 kernel with custom config.

Just wondering why kernel-2.6.32.23-170.xendom0.fc12.src.rpm cannot make itself into F14. It seems pretty stable. Why it cannot be just a package available via "yum install" . Anyway Fedora''s Libvirt has the best compatibility with Xen 4.0.1. It''s not too late switch back to Xen with PVOPS kernel. XenLinux 2.6.34.7 aka Suse is really dangerous . It outperforms pvops

2013/3/28 Anton Korobeynikov <asl at math.spbu.ru>: >> How can having an MSVC compatible compiler be to the detriment of clang and >> llvm? No one is trying to break mingw here, merely add support for something > Just to make stuff clear: I just wanted proper naming which will be > non-confusing. Right now we have: > - isTargetWindows() which really means

1. Attempt to load Nexenta under 2.6.32.16-1.2.108.xendom0.fc13.x86_64 Xen 4.0.1-rc6-pre & 2.6.32.16-1.2.108.xendom0.fc13.x86_64 on top F13 [root@fedora13 NexentaStor-Community-3.0.2]# uname -a Linux fedora13 2.6.32.16-1.2.108.xendom0.fc13.x86_64 #1 SMP Fri Jul 23 17:09:30 MSD 2010 x86_64 x86_64 x86_64 GNU/Linux [root@fedora13 NexentaStor-Community-3.0.2]# xm create -c

Hello, llvm-dev. thank you for your interest in my question. Currently, I compiled simple c source code (hello.c) in lunux and windows, and I tried to simple test . first case: hello.bc (compiled with "-emit-llvm" on windows) -> lli.exe(linux). second case: hello.bc (compiled with "-emit-llvm" on linux) -> lli.exe(windows). second case return good result. but First case

> How can having an MSVC compatible compiler be to the detriment of clang and > llvm? No one is trying to break mingw here, merely add support for something Just to make stuff clear: I just wanted proper naming which will be non-confusing. Right now we have: - isTargetWindows() which really means "msvc-compabile" - isTargetWin32() which means "everything on windows", so

> Sorry, this wasn't mentioned in documentation. llvm-gcc was built with > '--enable-threads' flag, thus it requires win32 pthread port. Keith have > already given a right link for dlls download. Just to make stuff clear: you'll have to download pthreadGC1.dll, rename it to pthreadGC.dll and put it somewhere in your PATH. All try to build all future versions of binaries

Hello, Prakash > I tried with --enable-languages=java and it still fails with the same > error: gcj is not supported by llvm-gcc (and even with build w/o LLVM, as you're doing) -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.

Hi! I'm making a strange observation in my backend, that ends in illegal code: Version 1: - I lower FrameIndex to TargetFrameIndex (nothing special) - I generate a special address-register ADD instruction in eliminateFrameIndex() to write FramePointer + offset into a new address-register - I use explicit load and store and address-registers in my target instruction patterns: eg (store

After upgrade via http://download.opensuse.org/repositories/Virtualization:/openSUSE11.3/openSUSE_11.3/src/xen-4.0.1_21326_01-1.1.src.rpm with any "kotd" or 2.6.34.4-2.2-xen VFB gets broken . It worked with original  Xen 4.0, no matter of  some additional patching to support ZFS 24 has been done and 4.0 src.rpm has been rebuilt to reinstall 4.0   In particular,  virt-install fails to

Hi Thanks for the info, it led to the source of the error I was having. I was using llvm-gcc binaries (built with mingw I guess) to compile a .c file that is my language runtime, llvm-link'ing that with my frontend's .ll, and using an vcpp-built lli to run the resulting bytecode. This caused the special case in X86RegisterInfo::emitPrologue for "main" to try to align the stack

Hi Anton, You're already a part of the llvm development team by participating actively on the llvm development list :) If you wish we can put you on: http://llvm.cs.uiuc.edu/Developers.html Great to have you on the team, welcome! We (Jeff, Morten, Paolo, the rest of the team and I) are looking forward to cooperate with you and to push win32 and mingw versions even further to stable and

Hello, Scott. > Checking the assembly from llc, the first alloca call is to allocate > local vars in _main. Is this just the state of the code at 2.0 when > built with vs.net, or is there something that I've managed to > mis-build locally? _alloca is used to probe the stack, if you asks for locals of size more that 4k. This is pretty ugly, but the names of this functions differs

Just surfing Net for 2-3 hr concerning "dracut" on Fedora 13. Several "warnings"  at the end of dmesg log. Seems like reaction on some system events scheduled to run on regular basis, but not user''s activity. Boris. --- On Tue, 8/17/10, Boris Derzhavets <bderzhavets@yahoo.com> wrote: From: Boris Derzhavets <bderzhavets@yahoo.com> Subject: Re: [Xen-devel]