search for: ir1

..., std::uint64_t end, float * __restrict__ c, float * __restrict__ a, float * __restrict__ b) { const std::uint64_t inner = 4; for (std::uint64_t i = start ; i < end ; i+=4 ) { { const std::uint64_t ir0 = ( ((i+0)/inner) * 2 + 0 ) * inner + (i+0)%4; const std::uint64_t ir1 = ( ((i+0)/inner) * 2 + 1 ) * inner + (i+0)%4; c[ ir0 ] = a[ ir0 ] + b[ ir0 ]; c[ ir1 ] = a[ ir1 ] + b[ ir1 ]; } { const std::uint64_t ir0 = ( ((i+1)/inner) * 2 + 0 ) * inner + (i+1)%4; const std::uint64_t ir1 = ( ((i+1)/inner)...

...ot the problem but just to let you know My /etc/resolv.conf nameserver 10.4.1.5 nameserver 10.4.1.2 search localhost Is this ok? following you will check my ping to yahoo: [root at localhost ~]# ping www.yahoo.com PING any-fp.wa1.b.yahoo.com (209.191.122.70) 56(84) bytes of data. 64 bytes from ir1.fp.vip.mud.yahoo.com (209.191.122.70): icmp_seq=0 ttl=54 time=346 ms 64 bytes from ir1.fp.vip.mud.yahoo.com (209.191.122.70): icmp_seq=2 ttl=54 time=383 ms 64 bytes from ir1.fp.vip.mud.yahoo.com (209.191.122.70): icmp_seq=3 ttl=54 time=380 ms 64 bytes from ir1.fp.vip.mud.yahoo.com (209.191.122.70):...

...d, float * __restrict__ c, float * __restrict__ a, float * __restrict__ b) > { > const std::uint64_t inner = 4; > for (std::uint64_t i = start ; i < end ; i+=4 ) { > { > const std::uint64_t ir0 = ( ((i+0)/inner) * 2 + 0 ) * inner + (i+0)%4; > const std::uint64_t ir1 = ( ((i+0)/inner) * 2 + 1 ) * inner + (i+0)%4; > c[ ir0 ] = a[ ir0 ] + b[ ir0 ]; > c[ ir1 ] = a[ ir1 ] + b[ ir1 ]; > } > { > const std::uint64_t ir0 = ( ((i+1)/inner) * 2 + 0 ) * inner + (i+1)%4; > const std::uint64_t ir1 =...

...* __restrict__ a, float * __restrict__ b) >> { >> const std::uint64_t inner = 4; >> for (std::uint64_t i = start ; i < end ; i+=4 ) { >> { >> const std::uint64_t ir0 = ( ((i+0)/inner) * 2 + 0 ) * inner + >> (i+0)%4; >> const std::uint64_t ir1 = ( ((i+0)/inner) * 2 + 1 ) * inner + >> (i+0)%4; >> c[ ir0 ] = a[ ir0 ] + b[ ir0 ]; >> c[ ir1 ] = a[ ir1 ] + b[ ir1 ]; >> } >> { >> const std::uint64_t ir0 = ( ((i+1)/inner) * 2 + 0 ) * inner + >> (i+1...

Hi Frank, > We are looking at a variety of target architectures. Ultimately we aim to run on BG/Q and Intel Xeon Phi (native). However, running on those architectures with the LLVM technology is planned in some future. As a first step we would target vanilla x86 with SSE/AVX 128/256 as a proof-of-concept. Great! It should be easy to support these targets. When you said wide-vectors I assumed

I require some help in debugging this code  library(neuralnet) ir<-read.table(file="iris_data.txt",header=TRUE,row.names=NULL) ir1 <- data.frame(ir[1:100,2:6]) ir2 <- data.frame(ifelse(ir1$Species=="setosa",1,ifelse(ir1$Species=="versicolor",0,""))) colnames(ir2)<-("Output") ir3 <- data.frame(rbind(ir1[1:4],ir2)) #rownames(ir3)<-c("SL","SW","PL&quo...

Hello my friends We are having seriously problems with our asterisk server, our versions are as follows: WANPIPE Release: 3.4.7 Asterisk 1.4.21.2 Zaptel Version: 1.4.11 libpri version: 1.4.10.2 The symptoms are very weird, the CLI stop working suddenly, a core show channels shows MANY channels FREEZED, the incoming and outgoing calls stop working, the internal calls stop working, in resume we

Hi all, The machine I am targeting has some special requirements for some operations, say: ADD or1, ir1, r5 would add ir1 (input reg 1) and r5 and put the result in or1 (output reg 1). The point id that input and output regs have to go paired (this meaning an addition of ir1 with whatever always goes to or1, or an in general irX + whatever goes to orX). AFAIK, InstrInfo.td only allow "$src = $...

...X tcp port 80 tcpdump: WARNING: Promiscuous mode not supported on the "any" device tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on any, link-type LINUX_SLL (Linux cooked), capture size 96 bytes 18:50:02.413280 IP tst-sniffer.qualcomm.com.49297 > ir1.fp.vip.sk1.yahoo.com.http: S 651414485:651414485(0) win 5840 <mss 1460,sackOK,timestamp 10144916 0,nop,wscale 7> 0x0000: 4500 003c 0741 4000 4006 d8c5 0a38 0635 E..<.A at .@....8.5 0x0010: 481e 022b c091 0050 26d3 cbd5 0000 0000 H..+...P&....... 0x0020: a00...

The debug messages are misleading. They should read “trying to vectorize a list of …”; The problem is that the SCEV analysis is unable to detect that C[ir0] and C[ir1] are consecutive. Is this loop from an important benchmark ? Thanks, Nadav On Oct 30, 2013, at 11:13 AM, Frank Winter <fwinter at jlab.org> wrote: > The SLP vectorizer apparently did something in the prologue of the function (where storing of arguments on the stack happens) which then...

...r(std::uint64_t start, std::uint64_t end, float * __restrict__ c, float * __restrict__ a, float * __restrict__ b) { const std::uint64_t inner = 4; for (std::uint64_t i = start ; i < end ; ++i ) { const std::uint64_t ir0 = ( (i/inner) * 2 + 0 ) * inner + i%4; const std::uint64_t ir1 = ( (i/inner) * 2 + 1 ) * inner + i%4; c[ ir0 ] = a[ ir0 ] + b[ ir0 ]; c[ ir1 ] = a[ ir1 ] + b[ ir1 ]; } } LV: Found a loop: for.body LV: Found an induction variable. LV: We need to do 0 pointer comparisons. LV: Checking memory dependencies LV: Bad stri...

...t;> kernel and distro, then I can only presume this is a bug, so my next >> step would be to raise this on the development list. > Just a guess, but our CPUID instruction might be translated to > assembly code differently. You can try running 'cpuid -ir' (or 'cpuid > -ir1' if it's the same on all cpus) on both machines, that will give > you the results libvirt is processing. If that output is different > than there is nothing libvirt can do. If it's the same, it might be a > libvirt bug. You might be onto something here. The following are run...

On Sep 7, 2010, at 3:01 AM, Carlos Sanchez de La Lama wrote: > The machine I am targeting has some special requirements for some > operations, say: > > ADD or1, ir1, r5 > > would add ir1 (input reg 1) and r5 and put the result in or1 (output reg > 1). The point id that input and output regs have to go paired (this > meaning an addition of ir1 with whatever always goes to or1, or an in > general irX + whatever goes to orX). > > AFAIK, Ins...

Well, they are not directly consecutive. They are consecutive with a constant offset or stride: ir1 = ir0 + 4 If I rewrite the function in this form void bar(std::uint64_t start, std::uint64_t end, float * __restrict__ c, float * __restrict__ a, float * __restrict__ b) { const std::uint64_t inner = 4; for (std::uint64_t i = start ; i < end ; ++i ) { const std::uint64_t ir0 = ( (...

...can only presume this is a bug, so my next >>>> step would be to raise this on the development list. >>> Just a guess, but our CPUID instruction might be translated to >>> assembly code differently. You can try running 'cpuid -ir' (or 'cpuid >>> -ir1' if it's the same on all cpus) on both machines, that will give >>> you the results libvirt is processing. If that output is different >>> than there is nothing libvirt can do. If it's the same, it might be a >>> libvirt bug. >> You might be onto somet...

...r(std::uint64_t start, std::uint64_t end, float * __restrict__ c, float * __restrict__ a, float * __restrict__ b) { const std::uint64_t inner = 4; for (std::uint64_t i = start ; i < end ; ++i ) { const std::uint64_t ir0 = ( (i/inner) * 2 + 0 ) * inner + i%4; const std::uint64_t ir1 = ( (i/inner) * 2 + 1 ) * inner + i%4; c[ ir0 ] = a[ ir0 ] + b[ ir0 ]; c[ ir1 ] = a[ ir1 ] + b[ ir1 ]; } } I was trying the following: clang++ -emit-llvm -S loop.cc -std=c++11 (this writes loop.ll) opt -O1 -bb-vectorize -debug loop.ll -S (I found the...

Hi Frank, The access pattern to arrays a and b is non-linear. Unrolled loops are usually handled by the SLP-vectorizer. Are ir0 and ir1 consecutive for all values for i ? Thanks, Nadav On Oct 30, 2013, at 9:05 AM, Frank Winter <fwinter at jlab.org> wrote: > The loop vectorizer seems to be not able to vectorize the following code: > > void bar(std::uint64_t start, std::uint64_t end, float * __restrict__ c, float...

...> > On 30/10/13 13:28, Renato Golin wrote: > > > > > On 30 October 2013 09:25, Nadav Rotem < nrotem at apple.com > wrote: > > > The access pattern to arrays a and b is non-linear. Unrolled loops > are usually handled by the SLP-vectorizer. Are ir0 and ir1 > consecutive for all values for i ? > > > Based on his list of values, it seems that the induction stride is > linear within each block of 4 iterations, but it's not a clear > relationship. > > > As you say, it should be possible to spot that once the loop is &gt...

...is is a bug, so my next > >>>> step would be to raise this on the development list. > >>> Just a guess, but our CPUID instruction might be translated to > >>> assembly code differently. You can try running 'cpuid -ir' (or 'cpuid > >>> -ir1' if it's the same on all cpus) on both machines, that will give > >>> you the results libvirt is processing. If that output is different > >>> than there is nothing libvirt can do. If it's the same, it might be a > >>> libvirt bug. > >> You...

...stro, then I can only presume this is a bug, so my next > >> step would be to raise this on the development list. > > Just a guess, but our CPUID instruction might be translated to > > assembly code differently. You can try running 'cpuid -ir' (or 'cpuid > > -ir1' if it's the same on all cpus) on both machines, that will give > > you the results libvirt is processing. If that output is different > > than there is nothing libvirt can do. If it's the same, it might be a > > libvirt bug. > You might be onto something here. Th...