similar to: LLVM 2.1 Release!

OK, so I pulled down the two MinGW32 binaries. I bzip2 -d the two into .tar files, then tar xvf them into my directory of choice. (C:/Prg/llvm-2.1 in this case.) When I run the compiler over hello.c, as per the Getting Started Guide, compilation works for both native and LLVM BC. When I run the native hello.exe, it works. When I try to run lli hello.bc, I get an unsatisfied DLL link error:

Hi All, Here is my current draft of the LLVM 2.1 release announcement. Unlike previous announcements, I'm not planning to largely duplicate the release notes in the announcement. In addition to this, I've checked in the first draft of the release notes into llvm/docs/ReleaseNotes.html (http://llvm.org/docs/ ReleaseNotes.html). I'd really appreciate it if anyone who

Hello John Wed, 26 Jul 2006 09:29:14 -0500 you wrote: > Reid Spencer wrote: > According to the web server error log, there's a syntax error in the > PHP script for that page. It looks like Patrick Jenkins made some > changes earlier today (aka last last night). Another thing: it seems, that GD support was broken. locgraph.php just trows and error. -- With best regards, Anton

misspellings: What's new, 1st paragraph: "nightly tester <http://llvm.org/nightlytest/>, llvm-config enhancEments"; 've found nothing wrong except of it :) On 8/8/06, Chris Lattner <sabre at nondot.org> wrote: > > > Hi All, > > Here's the first draft of the LLVM 1.8 release notes. Please take a look > and send me any comments or feedback you

FYI: It also showed up for ARM yesterday, but only for a non-debug build. On Mar 5, 2009, at 4:32 AM, Gabor Greif wrote: > Hi Bill, > > this might be a latent bug related to PPC. I have no such > machine to access atm., but I shall be able to reproduce the > problem when back at home. (In about 4 hours). > > I keep you informed. > > Cheers, > > Gabor >

Hi Bill, this might be a latent bug related to PPC. I have no such machine to access atm., but I shall be able to reproduce the problem when back at home. (In about 4 hours). I keep you informed. Cheers, Gabor On Mar 4, 7:57 pm, Bill Wendling <wendl... at apple.com> wrote: > Something last night broke the build on Darwin PPC. Possible Gabor's   > check-in? > > -bw

Something last night broke the build on Darwin PPC. Possible Gabor's check-in? -bw Begin forwarded message: > From: admin at spang.apple.com (admin) > Date: March 4, 2009 3:56:10 AM PST > To: wendling at apple.com > Subject: PPC Nightly Build Result > > /Volumes/SandBox/NightlyTest/llvmgcc42.roots/llvmgcc42~obj/obj- > powerpc-powerpc/./prev-gcc/xgcc

Reid, Click on any of these logs and you'll see the same asm parsing issues. It's been going on for much of the week. http://llvm.org/nightlytest/machines/2006-12-29_05:40:12-Build-Log.txt http://llvm.org/nightlytest/machines/2006-12-29_05:40:12-Build-Log.txt llvm[4]: Compiling stacker_rt.ll to stacker_rt.bc for Release build (bytecode)

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

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 >

Hi All, Here's the first draft of the LLVM 1.8 release notes. Please take a look and send me any comments or feedback you have: http://llvm.org/docs/ReleaseNotes.html Thanks! -Chris -- http://nondot.org/sabre/ http://llvm.org/

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

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

Reid Spencer wrote: > It seems after the change on Zion that the nightly test is broken. When > I go to http://llvm.org/nightlytest/, I get a blank page. Any ideas? > According to the web server error log, there's a syntax error in the PHP script for that page. It looks like Patrick Jenkins made some changes earlier today (aka last last night). This is the error that I get:

Jim Laskey wrote: > llvm[4]: Compiling stacker_rt.ll to stacker_rt.bc for Release build > (bytecode) > /Volumes/Muggles/LLVM/nightlytest/build/llvm/Release/bin/gccas: / > Volumes/Muggles/LLVM/nightlytest/build/llvm/projects/Stacker/lib/ > runtime/Release/stacker_rt.ll:21,0: parse error, expecting `LOAD' or > `STORE' >

> See llvm.org/nightlytest Many testers run various benchmarks > and produces comparison numbers daily. Can I trust those numbers? For example, right now I'm looking at http://llvm.org/nightlytest/machine.php?machine=230. "CVS checkout time" might be wrong, as LLVM is now in SVN. This column also jitters heavily. However, it's not really important. "Configure

Hey All, I have been making some changes to the nightly tester that will hopefully make debugging problems and performance issues easier. The big change is nightly test results will now be kept in a central location (http://llvm.org/nightlytest/index.php). I have committed a new file to utils/ called 'NewNightlyTest.pl'. It *should* behave almost exactly like the previous NightlyTest.pl

Actually, I'm talking about the shell that Perl invokes. When you run the NightlyTest.pl script, it uses Perl. The system() function in Perl invokes the "standard" shell to execute the command provided as the argument to system(). In NightlyTest.pl, I have changed the program to check out both the regular llvm CVS module as well as the llvm-test module. This command is what is

That makes sense. Someone should stick it in the coding standards? it's just thankless work Absolutely, but since slow compile times (can) nuke my productivity, I may move some code out of headers. Sincerely, Alexander Riccio -- "Change the world or go home." about.me/ariccio <http://about.me/ariccio> If left to my own devices, I will build more. ⁂ On Wed, Feb 10, 2016