similar to: unified register set question

does wine opens and works Babylon 8 well ??!! if i installed wine,will Babylon work well on it ?!! hope you will answer me thanks

The first patch will make "make install-strip" work. The second spends a few cycles avoiding "1 files to consider." Both are trivial but IMHO useful. --- Makefile.orig Wed Mar 13 06:38:42 2002 +++ Makefile Wed Mar 13 06:40:58 2002 @@ -12,6 +12,7 @@ LDFLAGS= INSTALLCMD=/bin/install -c +INSTALLMAN=/bin/install -c srcdir=. @@ -56,8 +57,8 @@ ${INSTALLCMD} -m 755 rsync

The BGL (Boost Graph Library) defines tie(), which is exactly what the tie() defined in STLExtras.h. The header files of GBL use boost::tie(), and other boost libraries use boost::tie() too. How to resolve the ambiguity for compiler? -- Tzu-Chien Chiu, 3D Graphics Hardware Architect <URL:http://www.csie.nctu.edu.tw/~jwchiu>

I've been doing some experiments with the Boost Graph Library (BGL) and interfacing to llvm's GraphWriter system. I'm using GBL for some custom work and needed a way to hook BGL's write_graphviz into GraphWriter to use the existing display infrastructure. To do this I added a HAVE_BOOST configure item and #ifdef'd the Boost support code in GraphWriter. Is this useful to

The following causes an assertion in recent svn pulls, but not in 2.5. The assertion: llvm-as: /home/bgl/work/llvm-work/include/llvm/ADT/SmallVector.h:125: T& llvm::SmallVectorImpl<T>::operator[](unsigned int) [with T = llvm::Constant*]: Assertion `Begin + idx < End' failed. The .ll code: target datalayout =

On Tue, 2012-05-01 at 19:58 -0500, Peter Bergner wrote: > On Tue, 2012-05-01 at 17:47 -0500, Hal Finkel wrote: > > By default it should build for > > whatever the current host is (no special flags required). To > > specifically build for something else, use: > > -ccc-host-triple powerpc64-unknown-linux-gnu > > or > > -ccc-host-triple

Hi, I'm a newbie trying to make an R program executable on UNIX, just like one would write an executable perl script by putting "#!/usr/bin/perl" in the first line, and so on. It seems, though, that this would only work if I use the "BATCH" command to tell R to execute the program in its first argument. This would have the unfortunately side-effect of dumping all

On Sat, 2012-05-12 at 00:47 -0500, Hal Finkel wrote: > On Tue, 01 May 2012 21:25:29 -0500 > Peter Bergner <bergner at vnet.ibm.com> wrote: > > By the strict letter of the 32-bit ABI, the save and restore of > > r31 at a negative offset of r1 is verboten. The ABI states the > > the stack space below the stack pointer is declared as volatile. > > I actually

We have a problem with shares that we would like to keep read-only for some users; it worked with 2.2.8a, but with 3.0.0 there is this odd behaviour: Users with read-only privilege can browse the files, can copy them out of the share (eg to their own hard disks) and open the copies, and can open the files in situ with Notepad; but if they try to open files in the share with Excel, for example, or

The following code works on 2.7, but causes an assertion on recent snapshots. Has something changed regarding bitcasts that makes this illegal? The code is: target datalayout = "e-p:32:32:32-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:32:32" target triple = "x86-unknown-unknown" @aa = global [32 x i8] zeroinitializer, align 1 @bb = global [16 x i8] zeroinitializer, align 1 define

On Tue, 01 May 2012 21:25:29 -0500 Peter Bergner <bergner at vnet.ibm.com> wrote: > On Tue, 2012-05-01 at 19:58 -0500, Peter Bergner wrote: > > On Tue, 2012-05-01 at 17:47 -0500, Hal Finkel wrote: > > > By default it should build for > > > whatever the current host is (no special flags required). To > > > specifically build for something else, use:

for Spam. In the process of setting up a more effective spam filtering system, I just noticed that bogofilter, which implements extensions of the (a?) "Naive Bayes" text classification approach, will dump out R data frames; the man page suggests how to "integrate" it with R for verification. (sort of, that is). Anyway, for those of you looking for silly and perhaps

The AVX saga continues. I am attempting to write a pattern for VEXTRACTF128 but am having some problems. My attempt looks something like this: defm EXTRACTF128 : avx_fp_extract_vector_osta_node_mri_256<0x19, MRMDestReg, MRMDestMem, "extractf128", undef, X86f32, X86i32i8, // rr [(set VR128:$dst,

hello, i need to use v32i32 and v32f32 in store instructions. I defined my register as; def VRR128 : RegisterClass<"X86", [v32i32, v32f32], 1024, (add R_0_V_0, R_1_V_0, R_2_V_0)>; def STORE_DWORD : I<0x70, MRMDestMem, (outs), (ins i2048mem:$dst, VRR128:$src), "STORE_DWORD\t{$src, $dst|$dst, $src}",

On Tue, 2012-05-01 at 17:47 -0500, Hal Finkel wrote: > By default it should build for > whatever the current host is (no special flags required). To > specifically build for something else, use: > -ccc-host-triple powerpc64-unknown-linux-gnu > or > -ccc-host-triple powerpc-unknown-linux-gnu So LLVM isn't biarch capable? Meaning one LLVM compiler cannot generate both

Hi All, I am in the process of writing an R extension in c++ and am using several STL containers (e.g., vector<double>, map<int, double>, multimap<int, double>). I make sure to clear all these containers at the end of the .Call. Everything compiles and runs just fine, but I'm a bit worried since I haven't found any other packages that use STL. So, my question: is it

I am trying to compile lustre like this : [onkar at localhost build-lustre]$ ./configure --with-kernel-source-header=/home/onkar/LUSTRE/linux-2.6.33.3/include --with-linux=/home/onkar/LUSTRE/linux-2.6.33.3 --with-linux-obj=/home/onkar/LUSTRE/linux-2.6.33.3 --with-linux-config=/home/onkar/LUSTRE/linux-2.6.33.3 checking build system type... i686-pc-linux-gnu checking host system type...

I am trying to compile lustre like this : [onkar at localhost build-lustre]$ ./configure --with-kernel-source-header=/home/onkar/LUSTRE/linux-2.6.33.3/include --with-linux=/home/onkar/LUSTRE/linux-2.6.33.3 --with-linux-obj=/home/onkar/LUSTRE/linux-2.6.33.3 --with-linux-config=/home/onkar/LUSTRE/linux-2.6.33.3 checking build system type... i686-pc-linux-gnu checking host system type...

Thank You. How to do the same for add please see the following; it gives duplication error. def VADD : I<0x0E, MRMDestReg, (outs VRR128:$dst), (ins VRR128:$src1, VRR128:$src2),"VADD\t{$src1, $src2, $dst|$dst, $src1, $src2}", [(set VRR128:$dst, (add VRR128:$src1, VRR128:$src2))]>, TA; def : Pat<(add VRR128:$src1, VRR128:$src2), (VADD VRPIM128:$src1, VRPIM128:$src2)>;

For future filesystem compatibility, we are wondering if there are any Lustre MDT filesystems in existence that have 2B or more total inodes? This is fairly unlikely, because it would require an MDT filesystem that is > 8TB in size (which isn''t even supported yet) and/or has been formatted with specific options to increase the total number of inodes. This can be checked with