similar to: [LLVMdev] LLVM and GCC 4.0

On Mon, 24 Oct 2005, Vladimir A. Merzliakov wrote: > I have some problems with build current CVS version LLVM using GCC 4.1.0 (GCC > CVS mainline version). Thanks! > 1) Build terminate with error: > > llvm[3]: Compiling SparcV8CodeEmitter.cpp for Debug build > /usr/home/wanderer/pkg/build/llvm/obj/lib/Target/SparcV8/SparcV8GenCodeEmitter.inc:11: > error: definition of

On Mon, 24 Oct 2005, Vladimir A. Merzliakov wrote: >>> 2) Same error but some diff. problem with AlphaCodeEmitter.cpp and >>> PPCCodeEmitter.cpp: >>> >>> GCC don't like definition member-functions in global namespace with >>> declaration in llvm::<unnamed> : > > Sorry for wrong comment. > Must be: > GCC 4.1.0 don't like

>> 2) Same error but some diff. problem with AlphaCodeEmitter.cpp and >> PPCCodeEmitter.cpp: >> >> GCC don't like definition member-functions in global namespace with >> declaration in llvm::<unnamed> : Sorry for wrong comment. Must be: GCC 4.1.0 don't like definition member-functions in llvm namespace with declaration in

Hi! I have some problems with build current CVS version LLVM using GCC 4.1.0 (GCC CVS mainline version). 1) Build terminate with error: llvm[3]: Compiling SparcV8CodeEmitter.cpp for Debug build /usr/home/wanderer/pkg/build/llvm/obj/lib/Target/SparcV8/SparcV8GenCodeEmitter.inc:11: error: definition of 'unsigned int

Hi! I can't build LLVM using GCC 4.1 (GCC CVS mainline) after http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20050328/025003.html Build terminated with error: /home/wanderer/pkg/build/llvm/src/llvm/lib/Target/SparcV9/ModuloScheduling/DependenceAnalyzer.cpp:25: error: explicit qualification in declaration of `llvm::FunctionPass* llvm::createDependenceAnalyzer()' at line:

Hi! After commit http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20060227/032167.html : - DIE *NewType(DIE *Unit, TypeDesc *TyDesc); + DIE *DwarfWriter::NewType(CompileUnit *Unit, TypeDesc *TyDesc); and http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20060227/032227.html - DIE *DwarfWriter::NewType(CompileUnit *Unit, TypeDesc *TyDesc); + DIE *DwarfWriter::NewType(DIE

In current state dates at small version of pictures generated by night builder script is unreadable ( for example http://llvm.cs.uiuc.edu/testresults/X86/running_loc.png ). I suggest rotate it to vertical position in small picture versions. .png file created modified gnuplot script (for comparing) and patch attached. "set xlabel 0,-1 " added for solving xlabel and xtics text overlap

Okay, I'll have to fix NightlyTest.pl not to use shell script syntax that isn't universal. Look for a commit soon. Reid. On Sun, 2004-09-05 at 13:31, Vladimir Merzliakov wrote: > > Bash 2.05b on Linux handles this fine. I was asking what > > your "default" system shell is on FreeBSD. Probably /bin/sh, right? > > Perhaps you can: > > > >

> Change the "rotate by 90" xtics specification to just "rotate" which is > equivalent. The "by <angle>" syntax is not acceptable for all output > devices. Apparently the Sparc and x86 output devices (no color) don't > accept this, but should accept the plain "rotate". Sorry, i must be more careful if i proposed patches. Vladimir

On Thu, 2004-09-02 at 00:04, Vladimir Merzliakov wrote: > I resend email with updated (after mass header move) log examples. > > > LLVM build without big problems in obj dir == src dir case (for example, > > last night tester build) > > But I have problem with building CVS version LLVM in obj dir != src dir > > case. I *only* build with obj dir != src dir and

----- Original Message ----- From: "Chris Lattner" <sabre at nondot.org> To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> Sent: Tuesday, March 08, 2005 6:31 PM Subject: Re: [LLVMdev] Recursive Types using the llvm support library > On Tue, 8 Mar 2005, Vladimir Merzliakov wrote: > >>>> An example where something really simple like the

>> Sorry for wrong comment. >> Must be: >> GCC 4.1.0 don't like definition member-functions in llvm namespace with >> declaration in <global>::<unnamed> namespace > > Ahhh, ok, I see. I just applied a patch to SparcV8. With it, does this > patch fix the problem? >- o << "namespace llvm {\n\n"; >+ //o <<

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

Vladimir, Thanks for the note. Unfortunately, the install approach that we're using in the makefiles is a bit broken, based on Linux install program. We'll get this cleaned up soon so that it works on multiple unixes. Reid. On Thu, 2005-02-17 at 14:48, Vladimir Merzliakov wrote: > Command from LLVM CFE bootstrap sequence at FreeBSD: > gmake -C runtime install-bytecode >

Result night tester run at FreeBSD 5.1 accessable by URL http://npt.cc.rsu.ru/testresults-X86-FreeBSD/index.html I can't guaranty run it per day base, sorry. As i can see, make (bug 385) and perl (bug 386) not builded by NightlyTest.pl (but builded if use gmake night tests run format) So I don't known preferable solutions: its can be closed or patches applied. Vladimir

On Fri, 25 Jun 2004, Vladimir Merzliakov wrote: > Result night tester run at FreeBSD 5.1 accessable by URL > http://npt.cc.rsu.ru/testresults-X86-FreeBSD/index.html > I can't guaranty run it per day base, sorry. Okay, sounds great. I added it to the page with a note to that effect: http://llvm.cs.uiuc.edu/testresults/ Thanks a lot for volenteering to run it. Also, if you notice

That's weird. What is your default shell that Perl invokes with the "system" command. This works fine with bash-2.05b. Reid. On Sun, 2004-09-05 at 10:01, Vladimir Merzliakov wrote: > > x86 FreeBSD: > > * hasn't run with changes yet > > I manually start script. I use this options (+ -verbose now for testing) > >

I think there is a very similar situation with the PowerPC/Mac OS X nightly tests. Over each of the past few nights, something has been filling up the process table, causing me to be unable to log in. The nightly tester wrote out regression test and feature test logs featuring hundreds of "Resource temporarily unavailable" errors from fork(), so I assume it's the qmtest

Just for information. After root update OS from FreeBSD 5.1 to FreeBSD 5.3-RC1 at make.cc.rsu.ru I don't rebuild LLVM C Frontend. Last LLVM build fail (2004-10-30) is result this situation. I update LLVM C Frontend and rerun manually nighttest script. All ok now :) Also, I think, "X86: FreeBSD 5.1 (may not be run every day)" line at

A typo in test/Makefile was the trigger for this problem: http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20041101/ 020216.html John, can you please look into this bug some more and add some error checking to the llvm-specific qmtest python modules to make this error less severe? Thanks! -Brian On Nov 3, 2004, at 10:35 AM, Brian Gaeke wrote: > > I think there is a very