similar to: [LLVMdev] IMPORTANT (Sparc): Switch-over to new C front-end

This is a note to let everyone know that I just changed the LLVM build scripts to use the new C front-end for everything (on X86). If you are doing development on X86, you *must* make the following changes to your setup: 1. Change your llvm-gcc symlink (or alias, or whatever you use) to point to ~lattner/local/x86/llvm-gcc/bin/gcc 2. Add the following environment variable to your startup

Here are a few bits of news about the C frontend: 1. I have ported it to compile and run under linux. On our research machines, it is available here: /home/vadve/lattner/cvs/gcc_install_x86 Note that this C compiler will still generate "64-bit" LLVM files, thus the code will probably not work right if run through the C backend, then compiled on x86. For middle-end

A new and improved C frontend is now available for experimentation. This is a C frontend that is based on the GCC AST representation as opposed to the old frontend which came from the RTL representation (which lost a lot of type information and caused other problems). I am still working on the new front-end, but it is remarkably stable for being so new. If you are interested in playing with it,

yue wrote: > hi, > about [LLVMdev] another question > > thanks > > yueqiang One other thing you might want to try is to put your object tree in a directory that is *not* inside of your source tree. Currently, we don't support using separate object trees that are subdirectories of the source tree. In other words: Will work: ========== SRC_ROOT=/home/yue/llvm

On Thu, 24 Jun 2004, Vladimir Merzliakov wrote: > At this moment I use > "gmake TEST=nightly" command line to run night tester > > What I must specific and where to disable SPEC run (i don't have it) I think that it's currently a bug that this does not automatically happen. > I known about new NightlyTest.pl option: -noexternals > But what I must do for

On Thu, 24 Jun 2004, Vladimir Merzliakov wrote: > > Are you using the NightlyTest.pl file? To run the tester I don't use > > gmake directly at all. Instead, I have this in my crontab: > > > > 5 3 * * * > LLVM_LIB_SEARCH_PATH=/home/vadve/lattner/local/x86/llvm-gcc/bytecode-libs > $HOME/llvm/utils/NightlyTest.pl -parallel -enable-linscan >

I'm encountering a new problem building llvm (from CVS) on Solaris. The tblgen executable builds successfully but it seems to use the wrong version of libstdc++ : % /home/vadve/vadve/llvm-sparc/Debug/bin/tblgen --help ld.so.1: /home/vadve/vadve/llvm-sparc/Debug/bin/tblgen: fatal: /home/ vadve/lattner/local/x86-fc1/gcc-3.4.2/lib/libstdc++.so.6: wrong ELF class: ELFCLASS32 Killed This

Hello. How are the things going with the llvm-gcc for SPARC and Solaris OS? I have discovered recently the fact, that the code is still in the "patches welcome" stage and is far even from being successfully built on SPARC. I would like to know, if anyone maintaining this code, what is the current to-do list, etc. I would like to offer my help for gcc front-end on SPARC project. --

> On Thu, 24 Jun 2004, Vladimir Merzliakov wrote: > > > At this moment I use > > "gmake TEST=nightly" command line to run night tester > > > > What I must specific and where to disable SPEC run (i don't have it) > > I think that it's currently a bug that this does not automatically happen. > > > I known about new NightlyTest.pl option:

Hello, I'm currently working on a project for the UC Berkeley in which a C++ file needs to be parsed that contains a new command. This new command is compiled to assembly, based on the SPARC V8, using a macro. On http://llvm.org/releases/1.8/docs/CFEBuildInstrs.html I read that inline assembly isn't supported. That page is last update 2 years ago. Does LLVM still not support inline

> Are you using the NightlyTest.pl file? To run the tester I don't use > gmake directly at all. Instead, I have this in my crontab: > > 5 3 * * * LLVM_LIB_SEARCH_PATH=/home/vadve/lattner/local/x86/llvm-gcc/bytecode-libs $HOME/llvm/utils/NightlyTest.pl -parallel -enable-linscan /home/vadve/shared/PublicCVS $HOME/buildtest-X86 $HOME/cvs/testresults-X86 > > When run like this,

FYI, I completely agree that we shouldn't remove the sparc target. However, it is currently unmaintained, and has some pretty glaring bugs. Is anyone interested in stepping up to maintain the target? -Chris On Oct 25, 2011, at 6:35 AM, Vikram Adve wrote: > Sparc is a popular target for architecture simulators, and removing that back end would force people using such simulators to use

On Sun, 12 Dec 2004, Reid Spencer wrote: > Hello, > > I need to solicit your opinion about something. > > I'm toying with the idea of getting rid of LLVM_LIB_SEARCH_PATH. Right > now the linkers will use this environment variable if it specifies a > single directory. It will look in that directory to find libraries when > things like -lc or -lcrtend are specified on

Sparc is a popular target for architecture simulators, and removing that back end would force people using such simulators to use some other compiler infrastructure. Sparc is also useful for University courses. I'd strongly discourage removing this back end. --Vikram Professor, Computer Science University of Illinois at Urbana-Champaign http://llvm.org/~vadve On Oct 25, 2011, at 4:00

Vladimir, Did the checkout fail? Its trying to do a chdir("llvm") in the build directory (second argument to the script) but that directory doesn't exist or isn't executable. Can you verify that you have an $HOME/pkg/build/llvm/night/build/llvm dir? Reid. On Thu, 2004-06-24 at 10:42, Vladimir Merzliakov wrote: > > Are you using the NightlyTest.pl file? To run the

Dear yueqiang, I tracked this down this morning, and it is a bug with our Python code that runs the tests. Essentially what is happening is that the code is finding the temporary directory it created the first time it ran the tests and believes that there are tests inside of it which it needs to run. It then gets confused and quits. This bug only shows up when the source tree and the

-----Original Message----- From: Vikram S. Adve [mailto:vadve at cs.uiuc.edu] Sent: Sunday, January 25, 2004 7:16 AM To: Joseph E. Grzywacz Subject: RE: [LLVMdev] Basic Blocks: Bytecode -> Native Code [Joseph, I'm sending this again because I didn't copy the list the first time.] Yes, this is true for the Sparc back-end. In fact, it is a fundamental assumption that is relied on by

Chris, > FYI, I completely agree that we shouldn't remove the sparc target. However, it is currently unmaintained, and has some pretty glaring bugs. Is anyone interested in stepping up to maintain the target? > > -Chris We can not let it die and I volunteer to keep the Sparc alive! My SPARCstation pizzaboxes can be ready for action in a day or two. Pawel Wodnicki > On Oct

Hi All, Do to popular request, I just set up a new mailing list to capture the nightly tester output from the various testers running 'round the world. The new list is available here: http://mail.cs.uiuc.edu/mailman/listinfo/llvm-testresults If you're running a nightly tester, please update your crontab to send mail to the llvm-testresults at cs.uiuc.edu list (potentially in addition

I'm done. Good to go. Good compile + new binaries all built against the latest OpenSSL libraries. Big thank you to James, Joseph Tam and Aki Tuomi who game me pointers and kept me in the right direction. ........................................................................ These are the settings that made everything work for me. First, needed a current, up-to-date version of OpenSSL