search for: do2

You can tell LLVM that you have "sign extended" setCC results (all ones). Dan On Nov 18, 2008, at 5:33 PM, Eli Friedman wrote: > On Tue, Nov 18, 2008 at 1:56 PM, Villmow, Micah > <Micah.Villmow at amd.com> wrote: >> The IR produces correct results, but my backend does not and the >> only thing >> I can think of is that the IR is treating the

...quot;,"s10","s11",..: 1 9 10 11 12 13 14 15 16 2 ... $ gp : Factor w/ 2 levels "gp1","gp2": 1 1 1 1 1 1 1 1 2 2 ... $ drug : Factor w/ 2 levels "dr1","dr2": 1 1 1 1 1 1 1 1 1 1 ... $ dose : Factor w/ 3 levels "do1","do2","do3": 1 1 1 1 1 1 1 1 1 1 ... > summary(aov(effect ~ gp * drug * dose + Error(subj/(dose+drug)), data=Ela.uni)) Error: subj Df Sum Sq Mean Sq F value Pr(>F) gp 1 270.01 270.01 7.0925 0.01855 * Residuals 14 532.98 38.07 --- Signif....

Hi Eli: Thank you very much for your comments! >> If you need some sort of unusual control flow construct, make it a >> proper terminator instruction I would love to. I was going by the advice in "docs/ExtendingLLVM.rst": "WARNING: Adding instructions changes the bitcode format, and it will take some effort to maintain compatibility with the previous

Hello, the following patches should get multidisk access working. The syntax accepted is the following: (hdx,y)/path/to/file where x is the disk number and start at 0 and the y is the partition number starting at 1. So (hd0,1) is the first partition of the first disk. the other accepted syntax is using MBR's 32 bits disk signature so for example: (mbr:0x12345678,2)/foo/bar would address

Hello list. I'm trying to rebuild the 2.6.9.67.0.20.EL kernel, but it fails even without modifications. How did I try it? Created a (non-root) build environment (not a mock ) Installed the kernel.scr.rpm and did a rpmbuild -ba --target=`uname -m` kernel-2.6.spec 2> prep-err.log | tee prep-out.log The build failed at the end: Processing files: kernel-xenU-devel-2.6.9-67.0.20.EL Checking