search for: 2.6

On Oct 21, 2009, at 3:44 PM, Tanya Lattner wrote: > Just a reminder that today is the last day for pre-release2 testing. > Hi Tanya, Attached are the log files for Mac OS X 10.5.8 on PowerPC. There are these failures for clang: ******************** Failing Tests (20): /Volumes/SandBox/2.6/llvm-2.6/tools/clang/test/CodeGen/ always_inline.c

Just a reminder that today is the last day for pre-release2 testing. Thanks, Tanya

Dear All- I have a dataset that is comprised of the following: doy yr mon day hr hgt1 hgt2 hgt3 co21 co22 co23 sig1 sig2 sig3 dif flag 244.02083 2005 09 01 00 2.6 9.5 17.8 375.665 373.737 373.227 3.698 1.107 0.963 -0.509 PRE 244.0625 2005 09 01 01 2.6 9.5 17.8 393.66 384.773 379.466 15.336 11.033 5.76 -5.307 PRE 244.10417 2005 09 01 02 2.6 9.5 17.8 411.162 397.866 387.755 6.835 5.61 6.728

On Oct 20, 2009, at 12:05 PM, Aaron Gray wrote: > 2009/10/20 Tanya Lattner <lattner at apple.com>: >> >> On Oct 20, 2009, at 5:49 AM, Jay Foad wrote: >> >>>> To test clang: >>>> 1) Compile llvm and clang from source. >>> >>> LLVM fails to build for me on Cygwin. I get: >>> >> >> Does TOT build? If not,

2009/10/20 Tanya Lattner <lattner at apple.com>: > > On Oct 20, 2009, at 12:05 PM, Aaron Gray wrote: > >> 2009/10/20 Tanya Lattner <lattner at apple.com>: >>> >>> On Oct 20, 2009, at 5:49 AM, Jay Foad wrote: >>> >>>>> To test clang: >>>>> 1) Compile llvm and clang from source. >>>> >>>> LLVM

Hi, I'm trying to build LLVM 2.6 (from svn branch release_26) on cygwin 1.7, and I have the following errors with both GCC 3.4.4 and GCC 4.3.4 llvm[2]: Linking Release Loadable Module profile_rt.dll /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../i686-pc-cygwin/bin/ld: warning: cannot find entry symbol __cygwin_dll_entry at 12; defaulting to 62fc1000

On Oct 20, 2009, at 5:49 AM, Jay Foad wrote: >> To test clang: >> 1) Compile llvm and clang from source. > > LLVM fails to build for me on Cygwin. I get: > Does TOT build? If not, please file a bug. Unfortunately Cygwin is not in our release criteria. I'd like to have a buildbot running (if there is not one already) and then get someone to qualify it for the

> To test clang: > 1) Compile llvm and clang from source. LLVM fails to build for me on Cygwin. I get: make[1]: Entering directory `/home/foad/llvm/objdir-2.6/runtime' make[2]: Entering directory `/home/foad/llvm/objdir-2.6/runtime/libprofile' llvm[2]: Compiling BasicBlockTracing.c for Release build (PIC) llvm[2]: Compiling BlockProfiling.c for Release build (PIC) llvm[2]:

2009/10/20 Tanya Lattner <lattner at apple.com>: > > On Oct 20, 2009, at 5:49 AM, Jay Foad wrote: > >>> To test clang: >>> 1) Compile llvm and clang from source. >> >> LLVM fails to build for me on Cygwin. I get: >> > > Does TOT build? If not, please file a bug. No. Theres the runtime install bug (below), and llvm-gcc has a bug that I

CC init/version.o LD init/built-in.o LD .tmp_vmlinux1 drivers/built-in.o: In function `vmcoreinfo_show'': /usr/src/linux-2.6.18-xen.hg/drivers/xen/core/xen_sysfs.c:340: undefined reference to `vmcoreinfo_size_xen'' /usr/src/linux-2.6.18-xen.hg/drivers/xen/core/xen_sysfs.c:340: undefined reference to `paddr_vmcoreinfo_xen'' make[4]: ** [.tmp_vmlinux1]

I am trying to build llvm-gcc4.2-2.6. My configure options are $ /local/tools/lin32/llvm-gcc4.2-2.6/bin/llvm-gcc -v Using built-in specs. Target: i686-linux Configured with: ../llvm-gcc4.2-2.6.source/configure --prefix=/local/tools/lin32/llvm-gcc4.2-2.6 --disable-nls --enable-shared --enable-threads=posix --enable-languages=c,c++ --with-gnu-as --with-gnu-ld --target=i686-linux

Hi! I compiled the xen-4.0.1 in Linux (Ubuntu 10.04), but as usually, the xen-4.1.0 is not behaving in a manner similar to the previous version. Am I required from version xen-4.1.0, transfer the kernel via the command "git clone git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.gitlinux-2.6-xen" from now? I mean, the "make prep-kernels" command of the xen-4.1.0 no

i_alloc_sem has always been a bit of an odd "lock". It''s the only remaining rw_semaphore that can be released by a different thread than the one that locked it, and it''s use case in the core direct I/O code is more like a counter given that the writers already have external serialization. This series removes it in favour of a simpler counter scheme, thus getting rid

Thanks for responding, Duncan, and clarifying that y'all need more info to help. I'm trying to compile binaries on os x 10.5.8 intel hardware that are compatible on ppc os x 10.4. When I include various flags to llvm-gcc, including: -m32 -arch ppc -isysroot /Developer/SDKs/MacOS10.4u.sdk -mmacosx-version-min=10.4 I am seeing errors when compiling using llvm-gcc 4.2. If I leave out

Processing commands for control at bugs.debian.org: > # sorry for the noise > submitter 585188 ! Bug #585188 [convirt] convirt: Python string exceptions no more allowed in Python 2.6 Changed Bug submitter to 'Sandro Tosi <morph at debian.org>' from 'Sandro Tosi <morph at ravel.debian.org>' > submitter 585189 ! Bug #585189 {Done: Julien BLACHE <jblache at

On Sep 8, 2009, at 2:53 PM, Chris Lattner wrote: > > On Sep 8, 2009, at 2:05 PM, Tanya Lattner wrote: >> This can not go into 2.6, because r79742 is not in 2.6: >> http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20090817/085284.html >> >> Should this really be a release candidate? Its changing quite a bit >> and its not causing a regression. >

I try to build llvm-gcc-4.2-2.6.source before build and install llvm-2.6, the configure is shown bellow ../llvm-gcc-4.2/configure --prefix=/home/ts/program/ --program-prefix=llvm- --enable-llvm=/home/ts/llvm/llvm-2.6 --enable-languages=c,c++ where, it is the path where llvm-2.6 source is stored, -enable-llvm=/home/ts/llvm/llvm-2.6 the "make" gave error message as bellow:

Hello, I notice llvm begin require python atleast 2.7, Then I saw the commit log >>> Require python 2.7. >>> >>> We were already requiring 2.5, which meant that people on old linux distros >>> had to upgrade anyway. >>> >>> Requiring python 2.6 will make supporting 3.X easier as we can use the 3.X >>> exception syntax. >>>

resend to larger group: which one is the right one? I''m going thru some merge hell and a need some newer PPC code from kernel.org. is it: http://xenbits.xensource.com/linux-2.6-xen.hg (worked on) --or-- http://xenbits.xensource.com/ext/linux-2.6-merge.hg (six weeks of nothing) there is also linux-2.6.rc-xen.hg, linux-2.6.tip-xen.hg, linux-2.6- patchqueue.hg the PPC team

On Sep 8, 2009, at 3:01 PM, Devang Patel wrote: > > On Sep 8, 2009, at 2:53 PM, Chris Lattner wrote: > >> >> On Sep 8, 2009, at 2:05 PM, Tanya Lattner wrote: >>> This can not go into 2.6, because r79742 is not in 2.6: >>> http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20090817/085284.html >>> >>> Should this really be a release