search for: 10i

...ithin 2^24 bytes of the instruction. It looks like the code generator should generate a jump using a function pointer in this situation and fails to handle this. Am I doing something wrong in my code or is this an LLVM bug? Jan Linux 64-bit: (gdb) print addone_addr $1 = (void *) 0x406018 (gdb) x/10i foo_addr 0x2b7184072030: sub $0x8,%rsp 0x2b7184072034: mov $0x14,%edi 0x2b7184072039: callq 0x2b7200406018 <--- absolutely not ok 0x2b718407203e: add $0x8,%rsp 0x2b7184072042: retq (gdb) x/10i nfoo_addr 0x40603a <nativefoo>: push %rbp 0x40603b <nativefoo+1&...

...$ gdb extlinux.elf (gdb) set architecture i8086 (gdb) target remote localhost:1234 Remote debugging using localhost:1234 0x0000fff0 in ?? () at localboot.inc:68 68 jmp kaboom ; If we returned, oh boy... How does "jmp kaboom" get here? We are at the BIOS entry point: (gdb) display/10i $cs*16+$eip 1: x/10i $cs * 16 + $eip 0xffff0: ljmp $0xf000,$0xe05b [...] (gdb) info symbol 0x7c00 bootsec in section .text (gdb) b bootsec Note: breakpoint -2 also set at pc 0x7c00. Breakpoint 1 at 0x7c00: file extlinux.asm, line 146. Breakpoint -2? That's new for me. Anyway: (gdb) c Cont...

I have found that the polyroot() function in R-1.1.1(both solaris and Win32 version) gives totally incorrect result. Here is the offending code: # Polyroot bug report: # from R-1.1.1 > sort(abs(polyroot(c(1, -2,1,0,0,0,0,0,0,0,0,0,-2,5,-2,0,0,0,0,0,0,0,0,0,1,-2,1)))) [1] 0.8758259 0.9486499 0.9731015 1.5419189 1.7466214 1.7535362 1.7589484 [8] 2.0216317 2.4421509 2.5098488 2.6615572

Prof Brian Ripley wrote: > This is intentional: it aligns the numbers. E.g. > > >options(width=12) > >print(c(1+1i, 1-10i, 1+100i)) > [1] 1+ 1i > [2] 1- 10i > [3] 1+100i > > Neat, eh? > > What made you think this was a bug? Ah ok, I've misunderstood this feature probably perhaps because, at first sight, I found the display looks "strange" when some of the numbers have large imag...

Good Evening We have been searching through the R documentation manuals without success on this one. What is the purpose or result of the "L" in the following? n=10 and n=10L or c(5,10) versus c(5L,10L) Thanks Joe Thanks Joe [[alternative HTML version deleted]]

...eck if they follow the linearity. I perform dynamic > instrumentation to compute the coefficients. Mh. I believe we should distinguish the data for Polly and for your calculations. I assumed we would use affine linear relations in the access functions (Actually isl_maps like {[i,j] -> List[10i + 30j + 10]) to define accesses such that Polly can use this access functions to calculate dependences and reschedule the code accordingly. The possibly non-affine accesses would then be hidden behind the virtual access. > However, for applying the transformations, Polly should either total...

Hi folks, I've been googling around for awhile but I can't seem to find an answer to my question. I have a number of filesystems that contain thousands of hard links due to some bad organization of data. Rsync, cpio and various other utilities fail to copy this data because I think there might be some cycles in it. (you know you have troubles if cpio can't copy it!) What I thought

Full_Name: Tom Short Version: 2.4.0 OS: Windows XP Submission from: (NULL) (68.236.159.227) It looks like there's a bug in acosh with complex number in windows: > acosh(2) [1] 1.316958 > acosh(2+0i) [1] 0+NaNi This happens for me on Windows XP with the following versions: R version 2.2.0, 2005-10-06, i386-pc-mingw32 R version 2.4.0 (2006-10-03) i386-pc-mingw32 It works fine with

This is exactly want I need to achieve with Polly actually. I think a good idea would be to define intrinsics / metadata, as you mentioned, to notify Polly that even though it cannot analyse these accesses, to ignore them and perform the code transformations. We can go even further and maybe describe these accesses with some parametric linear functions. For instance: while (cond1){

The message cannot be represented in 7-bit ASCII encoding and has been sent as a binary attachment.

...;- array( runif( 10000 ), c(100, 100)) > determinant <- function(x) prod(eigen(x)$values) > det1 <- function(x) prod(eigen(x, only.values = TRUE)$values) > det2 <- function(x) prod(diag(qr(x)$qr)) * (-1)^(ncol(x) - 1) > system.time(print(determinant(x))) [1] -27320631-8.050401e-10i [1] 0.06 0.04 0.00 0.00 0.00 > system.time(print(det1(x))) [1] 36072865748-5.155196e-06i [1] 0.06 0.00 0.00 0.00 0.00 > system.time(print(det2(x))) [1] -9.854994e+25 [1] 0.03 0.00 0.00 0.00 0.00 > all(eigen(x,only.values=TRUE)$values == eigen(x)$values) [1] FALSE > rel.diff <- functi...

On 25/08/2018 4:49 PM, Herv? Pag?s wrote: > The choice of the L suffix in R to mean "R integer type", which > is mapped to the "int" type at the C level, and NOT to the "long int" > type, is really unfortunate as it seems to be misleading and confusing > a lot of people. Can you provide any evidence of that (e.g. a link to a message from one of these

...n(llvm::Function*, llvm::MutexGuard const&) () #23 0x00000000006fe8fa in llvm::JIT::runJITOnFunctionUnlocked(llvm::Function*, llvm::MutexGuard const&) () #24 0x00000000006fead2 in llvm::JIT::getPointerToFunction(llvm::Function*) () #25 0x00000000004285e7 in main () at sprite.cpp:172 (gdb) x/10i $pc => 0x7565f0 <_ZNK4llvm20MachineJumpTableInfo12getEntrySizeERKNS_10DataLayoutE>: cmpl $0x5,(%rdi) 0x7565f3 <_ZNK4llvm20MachineJumpTableInfo12getEntrySizeERKNS_10DataLayoutE+3>: mov (%rdi),%edx 0x7565f5 <_ZNK4llvm20MachineJumpTableInfo12getEntrySizeERKNS_10DataL...

...const&) () > #23 0x00000000006fe8fa in > llvm::JIT::runJITOnFunctionUnlocked(llvm::Function*, llvm::MutexGuard > const&) () > #24 0x00000000006fead2 in llvm::JIT::getPointerToFunction(llvm::Function*) > () > #25 0x00000000004285e7 in main () at sprite.cpp:172 > (gdb) x/10i $pc > => 0x7565f0 > <_ZNK4llvm20MachineJumpTableInfo12getEntrySizeERKNS_10DataLayoutE>: cmpl > $0x5,(%rdi) > 0x7565f3 > <_ZNK4llvm20MachineJumpTableInfo12getEntrySizeERKNS_10DataLayoutE+3>: > mov (%rdi),%edx > 0x7565f5 > <_ZNK4llvm20MachineJumpTa...

I have a frontend that generates some LLVM bitcode that needs to be linked with other bitcode (its runtime library), which I generate from C++ source using Clang. If I write the output of my program to disk, link it with llvm-link, and then run it with lli, everything works perfectly. But if I try to perform the linking and running steps in my main program, I get this error during

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