search for: st0

...r). The MSVCRT `_ftol2` > function implements floating-point-to-unsigned conversion for i386 > targets, and LLVM 3.0 calls it with the cdecl calling convention for > `fptoui to i64` when targeting i386-pc-win32. However, it has its own > calling convention: The input value is taken from ST0 and popped off > of the x87 stack, and the return value is given in EDX:EAX. EAX, EDX, > and ST0 are clobbered (the latter by popping the stack). The function > creates a stack frame. It messes with the x87 control word internally, > but the original control word is restored before retu...

...t I know about so far). The MSVCRT `_ftol2` function implements floating-point-to-unsigned conversion for i386 targets, and LLVM 3.0 calls it with the cdecl calling convention for `fptoui to i64` when targeting i386-pc-win32. However, it has its own calling convention: The input value is taken from ST0 and popped off of the x87 stack, and the return value is given in EDX:EAX. EAX, EDX, and ST0 are clobbered (the latter by popping the stack). The function creates a stack frame. It messes with the x87 control word internally, but the original control word is restored before returning. -Joe

Hi, Hi, I have been googling, and can't find anything that will help me: mt -f /dev/st0 status /dev/st0: No such device or address Any suggestion? I am using CentOS 3 [RHEL ES3 without the licenses] The tape drive is recognized at boot [from dmesg] scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36 <Adaptec 29160 Ultra160 SCSI adapte...

On Jan 18, 2012, at 8:56 PM, Joe Groff wrote: > 2012/1/18 Jakob Stoklund Olesen <stoklund at 2pi.dk>: >> This should work: >> %1 = call i64 asm "call __ftol2", "=A,{st},~{dirflag},~{fpsr},~{flags},~{st}" (double %x) nounwind > > Forgive me for being slow, but what would be the best way to implement > the equivalent of that inline asm as a

Right. But there are 8 registers on the floating point stack from ST0 to ST7 and I think llvm is only using ST0 to ST6 in some code fragments. Could this be because of the assumption that X86::FP registers run from X86::FP0 to X86:FP6 ? --Aparna On Wed, May 25, 2011 at 2:28 PM, Jakob Stoklund Olesen <stoklund at 2pi.dk>wrote: > > On May 25, 2011, at...

My unit's firmware: library 05.03, tape d22h, shows the device as set to random mode. But mtx -f /dev/st0 status gives an error that google says the device is in sequential mode. dmesg|grep -i hp does reflect CentOS thinks the device is a sequential unit. I've tried this with Fedora 8, too, and both show the same, so it is either an issue with CentOS/Fedora RPMs, or the version of MTX? I&...

Dear guys, what is the best way to implement a swap of floating point registers in X86? For the integer registers, I am using xchg. Is there a similar instruction for floating point? My function to insert swaps is like: void X86RegisterInfo::swapRegs( MachineBasicBlock & mbb, MachineBasicBlock::iterator mi, unsigned r1, unsigned r2, const TargetRegisterClass

...;3/07, Fernando Magno Quintao Pereira <fernando at cs.ucla.edu> wrote: > > what is the best way to implement a swap of floating point registers > in X86? For the integer registers, I am using xchg. Is there a similar > instruction for floating point? FXCH swaps stN with st0, but you'd have to use memory for arbitrary swaps I believe. I have no idea if it's the "best" though. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20070703/a30f...

On May 25, 2011, at 12:08 PM, aparna kotha wrote: > Right. But there are 8 registers on the floating point stack from ST0 to ST7 and I think llvm is only using ST0 to ST6 in some code fragments. Could this be because of the assumption that X86::FP registers run from X86::FP0 to X86:FP6 ? Yes. My guess it that the code converting from FP to ST registers sometimes needs the extra stack slot. /jakob

...Thinking it wouldn't take that long, I opted not to run time before it. The fact that it is taking a long time, if I revisit the machine in the morning, what would be the best way to find out what time it ended? In this case, I'm using mt to erase an lto3 tape - sudo mt -f /dev/st0 erase. But I'd like to use the knowledge from this question to track other events, too. I feel like I should know this answer, but cannot think of the solution at the moment. Thanks. Scott

Greetings, Does anyone know if it is possible to give a guest domain access to character device hardware such as a SCSI tape drive (/dev/st0 | /dev/nst0)? I have recompiled the guest xenU kernel with hardware access and declared the pci SCSI card in the config file directive as follows: pci = [ ''4,3,0'' ] The log file when started reports: [2005-11-01 17:24:57 xend] DEBUG (XendDomainInfo:1178) Creating pc...

....dk> wrote: > Alright.  We definitely don't want to model it as a general call, then.  Normal calls clobber lots of registers. > > The options are: > > 1. Use a pseudo-instruction that X86FloatingPoint understands and turns into a call after arranging for the argument to be in ST0. >   You should emit: > >   %ST0 = COPY %vreg13; RFP80:%vreg13 >   %EAX, %EDX = FTOL2 %ST0<kill> >   %vreg16 = COPY %EAX<kill> >   %vreg17 = COPY %EDX<kill> > >   Then teach X86FloatingPoint that FTOL2 pops its argument, like FISTP64m. > > 2. Use inli...

...'0x0'/> </controller> I created tapedrive.xml with following contents: <disk type='block' device='lun' sgio='unfiltered'> <driver name='qemu' type='raw' cache='none'/> <source dev='/dev/st0'/> <target dev='st0' bus='scsi'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> I then attempt to attach using following command, and receive this error: # virsh a...

...7;controller> > > I created tapedrive.xml with following contents: > > <disk type='block' device='lun' sgio='unfiltered'> > <driver name='qemu' type='raw' cache='none'/> > <source dev='/dev/st0'/> > <target dev='st0' bus='scsi'/> > <address type='drive' controller='0' bus='0' target='0' unit='0'/> > </disk> > > I then attempt to attach using following command, and recei...

Hi, after installing centos 4.2 I've noticed that my internal Seagate scsi DAT 72GB tape drive hasn't been recognised in /media or doesn't show up in gnome when putting in a tape. Do I need to edit fstab first or load additional modules in the kernel during startup? regards, Geert -------------- next part -------------- An HTML attachment was scrubbed... URL:

...squid, 2 ldap servers , apache2, postgresql and others, 8 virtual machines at total in a hardware raid5. Now I need a backup system, and i will use bacula with a dell ultrium3 LTO. I would like to know if there are problems with i/o? How can I connect a DomU directly to /dev/st0 of Dom0 ?? Its a very good machine ( 4xXeon 4GB Ram ) , but i''m afraid to run bacula-fd in all DomUs and bacula-dir and bacula-sd in a DomU too, and get I/O problems, or may crash xen , corrupt data... whatever.... Someone Can help-me??? any help will be good..... thanks a lo...

I have an IDE based PC running Linux/CentOS4 to which I wish to attach a scsi dlt. The host controller is an Adaptec AHA3940 something that lspci reports as: SCSI storage controller: Initio Corporation 360P (rev 02). I would like to have the system load the driver for this adapter at boot but I have two problems: 1. I am not sure which driver to use; and 2. I do not know how to force

...rter(), and leaving the pseudo and call instructions side by side is not going to work. Just leave the pseudo-instruction alone until it hits X86FloatingPoint, where you can rewrite it. > Could this patch ever break in cases where the > operand's vreg doesn't happen to get mapped to ST0? Yes, exactly. You need to make some more complicated test cases. > I'm still a bit > foggy on the internals of X86FloatingPoint. Look at the code handling INLINE_ASM. You need to do the same, except you have fixed arguments STUses=1 and STClobbers=1, ST*=0. That should greatly simplif...

...vice = nv_device(subdev); + struct nouveau_engine *engine = NULL; struct nv50_fb_priv *priv = (void *)subdev; const struct nouveau_enum *en, *cl; + struct nouveau_object *engctx = NULL; + const int *poss_engines = NULL; + const char *client_name = "unk"; u32 trap[6], idx, chan; u8 st0, st1, st2, st3; int i; @@ -366,9 +388,34 @@ nv50_fb_intr(struct nouveau_subdev *subdev) } chan = (trap[2] << 16) | trap[1]; - nv_error(priv, "trapped %s at 0x%02x%04x%04x on channel 0x%08x ", + for (i = 0; i < ARRAY_SIZE(nvdev_engine_for_vm_engine); ++i) { + if (nvdev_en...

...d saved/restored all the xmm regs I >> added, however the calling code did not change at all... > > Look in X86InstrControl.td. The call instructions are all prefixed > by: > > let Defs = [RAX, RCX, RDX, RSI, RDI, R8, R9, R10, R11, FP0, FP1, FP2, > FP3, FP4, FP5, FP6, ST0, ST1, MM0, MM1, MM2, MM3, MM4, MM5, MM6, MM7, > XMM0, XMM1, XMM2, XMM3, XMM4, XMM5, XMM6, XMM7, XMM8, XMM9, XMM10, > XMM11, XMM12, XMM13, XMM14, XMM15, EFLAGS], > > This is the fixed list of call-clobbered registers. It should really > be controlled by the calling convention of the...