search for: timod

> See ix86_return_in_memory. (In 4.3 this is renamed to > return_in_memory_32.) > i128==TImode. But TImode should be used for __m128 stuff only there, not for integers. I'm looking into gfortran now. -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.

Anyone run across __fixunsdfti relocation problems while building the llvm gcc frontend on an AMD-64 box under linux? For some reason, TImode is turned on but the bootstrap xgcc compiler complains that 128-bit integers are not supported. Any clues on a workaround?

...or you may have to hack up some files in config/ i386) to disable gcc long double support? Evan On Oct 9, 2006, at 11:50 AM, Scott Michel wrote: > Anyone run across __fixunsdfti relocation problems while building the > llvm gcc frontend on an AMD-64 box under linux? For some reason, > TImode > is turned on but the bootstrap xgcc compiler complains that 128-bit > integers are not supported. > > Any clues on a workaround? > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > htt...

...t, wait for reply at which point the client hangs. ========================================================================= ===<truss -f -p 4415; 4455 is the pid of the child the segfaults>======== ... <snip> 4455: open("/dev/udp", O_RDWR) = 8 4455: ioctl(8, I_FIND, "timod") = 0 4455: ioctl(8, I_PUSH, "timod") = 0 4455: sigprocmask(SIG_SETMASK, 0xEFFFDD70, 0xEFFFDD60) = 0 4455: ioctl(8, I_STR, 0xEFFFDBE8) = 0 4455: sigprocmask(SIG_SETMASK, 0xEFFFDD60, 0x00000000) = 0 4455: ioctl(8, I_FLUSH, FLUSHRW) = 0 4455: sigprocmask(SIG_SETMASK, 0xEFFFDD70...

Hello, Does anyone know of any precedent for handling i128 in the calling convention on x86-32? I'm trying to write a testcase that returns an i128 value, and LLVM currently has only two 32-bit GPRs designated for returning integer values on x86-32. Dan

Ignore the suggested fix in my earlier post. How about this? diff --git a/lib/Target/X86/X86ISelLowering.cpp b/lib/Target/X86/X86ISelLowering.cpp index 20c81c3..b8ebf42 100644 --- a/lib/Target/X86/X86ISelLowering.cpp +++ b/lib/Target/X86/X86ISelLowering.cpp @@ -1632,10 +1632,11 @@ X86TargetLowering::X86TargetLowering(const X86TargetMachine &TM, if (!Subtarget.is64Bit()) { // These

I have Solaris 10 U7 that is exporting ZFS filesytem. The client is Solaris 9 U7. I can mount the filesytem just fine but I am unable to write to it. showmount -e shows my mount is set for everyone. the dfstab file has option rw set. So what gives? Phillip -- This message posted from opensolaris.org

Hi Folks, I''ve got a 3.9 Tb zpool, and it is casing kernel panics on my Solaris 10 280r (SPARC) server. The message I get on panic is this: panic[cpu1]/thread=2a100a95cc0: zfs: freeing free segment (offset=423713792 size=1024) This seems to come about when the zpool is being used or being scrubbed - about twice a day at the moment. After the reboot, the scrub seems to have