search for: j10

...an autoconf-based > build and see if they're somehow related to (triggered by) the way that > cmake builds LLVM? > > On the same machine autoconf build is fine where as cmake has failures, reproduced simply with cmake -DLLVM_ENABLE_ASSERTIONS=ON -DCMAKE_BUILD_TYPE=Release .. make -j10 make check-all -j10 Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20140401/8e83a943/attachment.html>

...a work-around did not help: Browse[2]> x <- model.matrix(formula(myform), as.matrix(p$data)) Error in model.frame.default(object, data, xlev = xlev) (from mice.R#601) : 'data' must be a data.frame, not a matrix or an array Browse[2]> formula(myform) ~educ_sg + ethnic_sg + hiv + J10 + A5 + mar_stat + orientation + Born_US ~ educ_sg + ethnic_sg + hiv + J10 + A5 + mar_stat + orientation + Born_US + (DWPAD_ActAvoid + DWPAD_EducConf + DWPAD_PasAvoid + DWPAD_Support) * ethnic_sg * racGayDiscStress + 0 Notice there are many three-way interactions, which certainl...

Erm, sheez having alot of problems :( I have just been reading all the archives on the mailing list for the past few hours and decided to try make the journal with: tune2fs -j -J10 /dev/hdc1 [root@tkw /]# tune2fs -j -J10 /dev/hdc1 tune2fs 1.20-WIP, 17-Jan-2001 for EXT2 FS 0.5b, 95/08/09 Creating journal inode: done [root@tkw /]# cat /etc/fstab /dev/hdc1 /usr/local ext3 defaults 0 0 [root@tkw /]# mount /dev/hdc1 mount: wrong fs type, bad option, bad superblock on /dev/hdc1...

...'re somehow related to > (triggered by) the way that cmake builds LLVM? > > > > > On the same machine autoconf build is fine where as cmake has > failures, reproduced simply with > > > cmake -DLLVM_ENABLE_ASSERTIONS=ON -DCMAKE_BUILD_TYPE=Release .. > make -j10 > make check-all -j10 > > > Did you have a chance to test with cmake? Current clang trunk still > shows 47 test failures on our PPC64 systems. Unfortunately no, this is on my TODO list, but I've not gotten to it yet. Hopefully next week. -Hal > > > Thanks. >...

...gt; > >> > >> > >> > >> > On the same machine autoconf build is fine where as cmake has >> > failures, reproduced simply with >> > >> > >> > cmake -DLLVM_ENABLE_ASSERTIONS=ON -DCMAKE_BUILD_TYPE=Release .. >> > make -j10 >> > make check-all -j10 >> > >> > >> > Did you have a chance to test with cmake? Current clang trunk still >> > shows 47 test failures on our PPC64 systems. >> >> Unfortunately no, this is on my TODO list, but I've not gotten to it yet....

Hi, > OK, not quite sure what this means about my system tools. Is there > something I should be concerned about? it seems that a bug in your system tools happens to be tickled by LLVM. We can't do much about the fact that your system doesn't work properly, though if enough people see a problem we do sometimes try to tweak LLVM so it avoids triggering the bug. If you don't

Try: make check-all LIT_ARGS="-s -j10" To limit the threads to 10, for example. On Wed, Jan 16, 2013 at 1:38 PM, Redmond, Paul <paul.redmond at intel.com> wrote: > Hi, > > Does anyone know how I can set the number of threads lit uses when invoked by make check? Lit has the —threads argument but this doesn't ge...

Hi, On Wed, Mar 26, 2014 at 4:19 PM, Hal Finkel <hfinkel at anl.gov> wrote: > > Okay, interesting. I also did a build with -mcpu=ppc64 and did not observe > these issues. What standard C++ library are you building against? > I disabled assertions and the number of failures halved but Debuginfo failures looks very weird. Don't know if it helps to debug the issue at hand.

Hi, Does anyone know how I can set the number of threads lit uses when invoked by make check? Lit has the —threads argument but this doesn't get set when run through make so it uses the max number of cpus. paul

>> $ make -j15 > > do you really have 15 CPUs?  If not, this will most > likely just slow things down. > I have 8 CPUs. I started with -j8 and turned the knob up a bit. It seemed to run faster, so I stuck with j15. I guess there might be some context switching when threads are blocking on memory or IO. I could be imagining the speedups though because of some sort of placebo

I have a broadcom bcm5722 and a dual intel pro/1000 pt nic in a dell t110. The setup sees the cards and i put them into automatic mode. After the install no cards are detected at all. Astaro 8.01 detects and utilizes all of these cards just fine. I have also tried ubuntu server 10.04 lts and they work fine. I'm curious if this is a bug with Centos 6?

hi everyone : i'm not sure if my previous mail about this got sent. i was typing and erroneosuyl hit a button and lost what i was typing. anyway, i have the code below ( it works ) in which i run through the rows of a dataframe, taking out the first two fields which are characters strings ( with some extra spacing so i yuse gsub) and appending these character strings to a list so that i can

To whom it may concern, I'm Utsav Parmar, pursuing my B. Tech in Computer Engineering. I like to work on new technologies and am currently looking for open-source projects to contribute to. As it may turn out, I've got a college project in my curriculum this semester under “Software Development Practice”, and I'd like to work upon a project and/or a feature in pipeline spanning over

Hi, cross-compiling LLVM on the ppc64 architecture fails with: make[1]: *** No rule to make target `../build/llvm-r204075/BuildTools/Debug+Asserts/bin/llvm-tblgen', needed by `../build/llvm-r204075/lib/IR/Debug+Asserts/Intrinsics.gen.tmp'. Stop. make[1]: *** Waiting for unfinished jobs.... this fails for me for r204075 (today) and r203443. Configuration details: $LLVMPATH/configure

IRIX 6.5.22, compiled omega.0.8.1 with native MIPS compiler. omega.cgi isn't running from apache. From the log: [Wed Sep 1 10:04:36 2004] [error] [client 198.149.32.31] malformed header from script. Bad header=Caught unknown exception: /var/www/cgi- bin/omega.cgi This is with a url of http://<machine>/cgi-bin/omega.cgi?DB=/open/ When I run it from the command line with no

..."h3", "h4", "h5", "h6", "h7", "h8", "h9", "i1", "i10", "i2", "i3", "i4", "i5", "i6", "i7", "i8", "i9", "j1", "j10", "j2", "j3", "j4", "j5", "j6", "j7", "j8", "j9", "k1", "k10", "k2", "k3", "k4", "k5", "k6", "k7", "k8", "k9&...