search for: 8193

Full_Name: Paul Bailey Version: 2.1.1 OS: OS X 10.3 Submission from: (NULL) (68.252.250.144) ?cor [tells me that it has a na.rm variable] > cor(frame2[1,],frame2[2,],na.rm=T) Error in cor(frame2[1, ], frame2[2, ], na.rm = T) : unused argument(s) (na.rm ...) hmm.

On Tue, Jan 24, 2017 at 1:20 PM, Sanjay Patel via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > I started looking at the log files that you attached, and I'm confused. > The code that is supposedly causing the perf regression is created by the > loop vectorizer, right? Except the bad code is not in the "vector.body", so > is there something peculiar about

...c16.for.body5_crit_edge ], [ 2, %for.cond.preheader ] %2 = add i64 %indvar, 2 %3 = shl i64 %indvar, 1 %4 = add i64 %3, 4 %5 = add i64 %indvar, 2 %6 = shl i64 %indvar, 1 %7 = add i64 %6, 4 %8 = add i64 %indvar, 2 %9 = mul i64 %indvar, 3 %10 = add i64 %9, 6 %11 = icmp sgt i64 %10, 8193 %smax = select i1 %11, i64 %10, i64 8193 %12 = mul i64 %indvar, -2 %13 = add i64 %12, -5 %14 = add i64 %smax, %13 %15 = add i64 %indvar, 2 %16 = udiv i64 %14, %15 %17 = add i64 %16, 1 %tobool7 = icmp eq i8 %1, 0 br i1 %tobool7, label %for.inc16, label %if.then ====================...

I think I posted this patch before, but it looks like it was in December 2012 (!). 1/1 libxl: introduce an option for disabling the non-O_DIRECT workaround Ideally it would go into 4.4, at least. Provided the corresponding qemu part has gone into qemu-xen, which I think it has. Can anyone confirm ?

...) The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> # e2fsck -f 8193 /dev/hda8 Usage: e2fsck [-panyrcdfvstDFSV] [-b superblock] [-B blocksize] [-I inode_buffer_blocks] [-P process_inode_size] [-l|-L bad_blocks_file] [-C fd] [-j external_journal] [-E extended-options] device Emergency...

...information in the registry for bias 180, std (d/m/y): 17/02/2008, dlt (d/m/y): 12/10/2008 fixme:process:IsWow64Process (0xffffffff 0x5d7a6c) stub! fixme:system:SystemParametersInfoW Unimplemented action: 8192 (SPI_GETFOREGROUNDLOCKTIMEOUT) fixme:system:SystemParametersInfoW Unimplemented action: 8193 (SPI_SETFOREGROUNDLOCKTIMEOUT) fixme:volume:GetVolumePathNameW (L"I:\\ewb_temp\\support\\NISysInf.dll", 0x7263f8, 34), stub! err:ole:CoGetClassObject class {5b9cece7-5b14-44da-a00b-d38c3c97fe66} not registered err:ole:CoGetClassObject class {5b9cece7-5b14-44da-a00b-d38c3c97fe66} not r...

...The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> Trying e2fsck -b 8193 /dev/sdb1 gives the same result. # tune2fs -l /dev/sdb1 tune2fs 1.35 (28-Feb-2004) tune2fs: Bad magic number in super-block while trying to open /dev/sdb1 Couldn't find valid filesystem superblock. I tried turning on EFI_PARTITION in the kernel and rebu...

...pdate: 0 Replacing.3 0x88ca250: i32 = shl 0x88ca3e0, 0x88ca1e8 With: 0x88ca3e0: i32,ch = load 0x88c8f30, 0x88c8bf0, 0x88c9130 Lowered selection DAG: SelectionDAG has 12 nodes: 0x88ca3e0: <multiple use> 0x88c8c88: i8 = Constant <1> 0x88ca478: i32 = GlobalAddress <[8193 x i8]* @flags.2176> 0 0x88ca3e0: <multiple use> 0x88ca2b8: i32 = add 0x88ca478, 0x88ca3e0 0x88c9130: <multiple use> 0x88c8cf0: ch = store 0x88ca3e0:1, 0x88c8c88, 0x88ca2b8, 0x88c9130 0x88c8bf0: <multiple use> 0x88c9130: <multiple use> 0x8...

...ortex-A15 LNT machines Thanks for letting me know about this problem! There's no 'shl nsw' visible in the earlier (r292487) code, so it would be better to see exactly what the IR looks like before that added transform fires. But I see a red flag: %smax = select i1 %11, i64 %10, i64 8193 The new icmp transform allowed us to create an smax, but we have this hack in InstCombiner::visitICmpInst(): // Test if the ICmpInst instruction is used exclusively by a select as // part of a minimum or maximum operation. If so, refrain from doing // any other folding. This helps out other...

...ystem to ext3 and is working fine for a couple of weeks. However, I did a silly thing when I e2fsck (version 1.23) an ext3 /home partiction without umounting it. Now, I believe my partiton super-block is corrupted and the system wasn't able to mount /home. I tried as suggested to do a e2fsck -b 8193 /dev/hdaX but returned with the "bad magic numer in super-block while trying to open /dev/hdaX". I've also tried debugfs and have the same error. As I've data on /home partition, I would very much hope to recover it. Short of doing a make2fs to create a new ext3 partition, is this...

...ortex-A15 LNT machines Thanks for letting me know about this problem! There's no 'shl nsw' visible in the earlier (r292487) code, so it would be better to see exactly what the IR looks like before that added transform fires. But I see a red flag: %smax = select i1 %11, i64 %10, i64 8193 The new icmp transform allowed us to create an smax, but we have this hack in InstCombiner::visitICmpInst(): // Test if the ICmpInst instruction is used exclusively by a select as // part of a minimum or maximum operation. If so, refrain from doing // any other folding. This helps out other...

Can anyone point me in the right direction for correcting errors on an HD when using LVM? I've tried e2fsck and indicates bad block. I've tried with -b 8193, 16384, and 32768 and no good. I've found some info about reiserfsck on google, but this utility doesn't seem to be included in Centos4.3. I did find it on my old FC1 box. I am thinking now I really should have went with just regular 83 Linux ext3 partitions. Arrgghhh. And if I want to...

...T is crashing randomly now. There doesn't seem to be any reason, or reproducible thing that I can do to make it crash, it just decides it has had enough, and crashes. Here is one output from the terminal when it crashed. wine act.exe fixme:system:SystemParametersInfoW Unimplemented action: 8193 (SPI_SETFOREGROUNDLOCKTIMEOUT) fixme:atl:AtlModuleInit SEMI-STUB (0x18d7328 0x18d7020 0x18d0000) err:dc:CreateDCW no driver found for L"" err:x11drv:X11DRV_CreateWindow invalid window width -15 err:x11drv:X11DRV_CreateWindow invalid window height -20 err:x11drv:X11DRV_CreateWindow invalid...

...ex for repository > http://www.stats.ox.ac.uk/pub/RWin/bin/windows/contrib/2.2 > Error in install.packages(NULL, .libPaths()[1], dependencies = TRUE, > type = type) : > no packages were specified Best regards, Peter Arnold, CFA President PRA Investment Counsel, Inc. 704-341-8193 www.prainvestment.com

...ortex-A15 LNT machines Thanks for letting me know about this problem! There's no 'shl nsw' visible in the earlier (r292487) code, so it would be better to see exactly what the IR looks like before that added transform fires. But I see a red flag: %smax = select i1 %11, i64 %10, i64 8193 The new icmp transform allowed us to create an smax, but we have this hack in InstCombiner::visitICmpInst(): // Test if the ICmpInst instruction is used exclusively by a select as // part of a minimum or maximum operation. If so, refrain from doing // any other folding. This helps out other...

Hello, We have a 3-node cluster setup with ocfs2. Since friday one of the nodes went down and would not become clustermember after a reboot because it was unable to write to the ocfs2 filesystem. Message: no space left on device. There is plenty of diskspace though. No problem whatsoever to create a file / directory on the filesystem using one of the other nodes. Today one of the remaining

Hello, I had a scientific linux 3.0.4 system (rhel compatible), with 3 ide disks, one for / and two others in linear raid (250 gb and 300 gb each). This system was obsoleted so i move the raid disks to a new scientific linux 3.0.7 installation. However, the raid array was not detected ( I put the disks on the same channels and same master/lsave setup as in the previous setup). In fact

...essfull version was 20050310. For testing I can propose one example : http://hem.bredband.net/alivor/ichat121b6.exe Now I try to use wine 0.9.1 under FreeBSD (KDE 3.4.0). The application above is installed fine but during start I see: fixme:system:SystemParametersInfoW Unimplemented action: 8193 (SPI_SETFOREGROUNDLOCKTIMEOUT) I switch to application window: fixme:system:SystemParametersInfoW Unimplemented action: 4118 (SPI_GETTOOLTIPANIMATION) fixme:system:SystemParametersInfoW Unimplemented action: 4120 (SPI_GETTOOLTIPFADE) fixme:win:AnimateWindow partial stub These messages...

...: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> This happens whatever device I use for root partition in domU /etc/fstab (/dev/sda1 or /dev/xdva1). However, I can perfectly mount /dev/vg0/sexonthebeach as an ext3 partition in domU. Morevoer, the emergency shell has expected content monted under / in both case... Last question...

susan@susan:~/.wine/dosdevices/e:$ wine setup.exe susan@susan:~/.wine/dosdevices/e:$ fixme:seh:check_no_exec No-exec fault triggered at 0x1a082000, enabling work-around err:ntdll:RtlpWaitForCriticalSection section 0xa5125590 "?" wait timed out in thread 0012, blocked by 0000, retrying (60 sec) susan@susan:~/.wine/dosdevices/e:$ err:ntdll:RtlpWaitForCriticalSection section 0xa5125590