search for: n16

hello: I have 3 data.frame objects. First df object: Of dim (149,31). Columns 2:31 are marked as T1..T14 and N1..N16. Name T1 T2 N1 T3 N2 N3 N4 T4 mu1 10 10 9 10 9 9 8 10 mu2 11 11 9 11 9 9 9 11 ... muN 12 12 9 11 9 9 8 12 Second df object: of Dim (50000,31). Columns 2:31 are maked as T1...T14 and N1..N16. Name T1 T2...

It's not clear what is actually wrong from your original message, I think you need to give some more information as to what you are doing: Example source, what target GPU, compiler error messages or other evidence of "it's wrong" (llvm IR, disassembly, etc) ... -- Mats On 8 April 2016 at 09:55, Liu Xin via llvm-dev <llvm-dev at lists.llvm.org> wrote: > I built it

...//files.lancethepants.com/Firmware/ Source here. https://github.com/lancethepants/Toastman-Tinc I made a good handful of images for MIPSR2 routers with 8MB+ flash Linksys E900 Linksys E1200v2 Linksys E1500 Linksys E1550 Linksys E2000 Linksys E2500 Linksys E3000 Linksys E3200 Linksys E4200 Asus RT-N16 (tomato-K26USB-1.28...) Belkin F7D8301 (Same firmware as RT-N16) Asus RT-N66U/R (tomato-K26USB-NVRAM64K) Probably other broadcom supported Tomato routers too. Please make sure you flash the correct image. I can't be responsible if you brick your router. I'm using this on RT-N16, Belkin F7...

Here's the IR I'm trying to compile for my backend, a 16-bit CPU: ; ModuleID = 'foo.c' source_filename = "foo.c" target datalayout = "E-m:e-p16:16:16-i1:16:16-i8:16:16-i16:16:16-i32:16:16-i64:16:16-S16-n16" target triple = "tms9900" @global_var = common global i16 0, align 2 ; Function Attrs: noinline nounwind optnone define signext i16 @dothis(i16 signext %a) #0 { entry: %a.addr = alloca i16, align 2 store i16 %a, i16* %a.addr, align 2 %0 = load i16, i16* @global_var, align 2...

...o common, but as an example) to 192.168.1.5, and then have 192.168.1.5 listen on port 2222? Then have a firewall rule to allow access on that port and edit /etc/ssh/sshd_config to listen on 2222 instead of 22. Looking at http://nextgendigitalhome.com/1829/home-network/scalable-gateway/the-asus-rt-n16-router-firmware-part-4-advanced-wan-settings/ it seems as if it would allow this and it's described in the section WAN Virtual Server/Port Fowarding. -- Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6

Hi, I am backing up about 500G of data from a linux-based NAS to a USB hard drive attached to a router (rt-n16 with tomatousb firmware). Both NAS and the router have rsync-3.0.9. The router is running rsync in the daemon mode. To test the set up, I rsync'd the files to the empty USB hard drive, then back to the NAS in a new temp dir. Afterwards, I did a local "diff -r" on the NAS. To my surpri...

...'ve set up a port forwarding rule on the router that forwards incoming port 22 to port 9 on the LAN side of the router. As I understand it, port 9 is a /dev/null equivalent, and it seems to block the port well enough, but are there caveats I should be aware of? thanks! BTW, this is an Asus RT-N16 router using their latest released firmware. Fred -- ---- Fred Smith -- fredex at fcshome.stoneham.ma.us ----------------------------- The Lord is like a strong tower. Those who do what is right can run to him for safety. --------------------------- Proverbs...

...k? Any ideas how to get it working? Important for our target applications. Thanks, - Dima. $ cat test.ll ; ModuleID = '__kernelgen_main_module' target datalayout = "e-p:64:64:64-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-v16:16:16-v32:32:32-v64:64:64-v128:128:128-n16:32:64" target triple = "nvptx64-unknown-unknown" @yweek.1533 = internal global [7 x [3 x i8]] [[3 x i8] c"MON", [3 x i8] c"TUE", [3 x i8] c"WED", [3 x i8] c"THU", [3 x i8] c"FRI", [3 x i8] c"SAT", [3 x i8] c"SUN"]...

...not sure what I'm supposed to do with "LLVM ERROR: Cannot select: t1: i16 = Constant<127>".BTW, the function is: ; ModuleID = 'return.c' source_filename = "return.c" target datalayout = "E-m:e-p:16:16:16-i1:16:16-i8:16:16-i16:16:16-i32:16:16-i64:16:16-S16-n16" target triple = "tms9900" ; Function Attrs: noinline nounwind optnone define signext i16 @my_func() #0 { entry: ret i16 127 } ------- debug output -------- Optimized legalized selection DAG: BB#0 'my_func:entry' SelectionDAG has 5 nodes: t0: ch = EntryToken t3: ch...

...discovered that, in fact, reassociate seems broken, > and should be doing the right thing on most of your testcases. > > Let's take nary-add.ll, left_reassociate > > ; RUN: opt < %s -nary-reassociate -S | FileCheck %s > > target datalayout = "e-i64:64-v16:16-v32:32-n16:32:64" > > declare void @foo(i32) > > ; foo(a + c); > ; foo((a + (b + c)); > ; => > ; t = a + c; > ; foo(t); > ; foo(t + b); > define void @left_reassociate(i32 %a, i32 %b, i32 %c) { > %1 = add i32 %a, %c > call void @foo(i32 %1) > %2 = add i32...

...ons. >> >> Thanks, >> - Dima. >> >> $ cat test.ll >> ; ModuleID = '__kernelgen_main_module' >> target datalayout = >> "e-p:64:64:64-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-v16:16:16-v32:32:32-v64:64:64-v128:128:128-n16:32:64" >> target triple = "nvptx64-unknown-unknown" >> >> @yweek.1533 = internal global [7 x [3 x i8]] [[3 x i8] c"MON", [3 x >> i8] c"TUE", [3 x i8] c"WED", [3 x i8] c"THU", [3 x i8] c"FRI", [3 x >> i8]...

...ERROR: Cannot select: t1: i16 = >> Constant<127>".BTW, the function is: >> >> ; ModuleID = 'return.c' >> source_filename = "return.c" >> target datalayout = >> "E-m:e-p:16:16:16-i1:16:16-i8:16:16-i16:16:16-i32:16:16-i64:16:16-S16-n16" >> target triple = "tms9900" >> >> ; Function Attrs: noinline nounwind optnone >> define signext i16 @my_func() #0 { >> entry: >> ret i16 127 >> } >> >> ------- debug output -------- >> >> Optimized legalized select...

...add the Module > from the host compilation to my JIT as usual, but... what to do with the > Module from the device compilation? If I just add it to the JIT, I get an > error message like this: > > Added modules have incompatible data layouts: > e-i64:64-i128:128-v16:16-v32:32-n16:32:64 (module) vs > e-m:e-p270:32:32-p271:32:32-p272:64:64-i64:64-f80:128-n8:16:32:64-S128 (jit) > > Any suggestions as to what to do with the Module containing CUDA kernel > code, so that the host Module can invoke it? > > Geoff > > On Tue, Nov 17, 2020 at 6:39 PM Geoff Lev...

We have an application that allows the user to compile and execute C++ code on the fly, using Orc JIT v2, via the LLJIT class. And we would like to extend it to allow the user to provide CUDA source code as well, for GPU programming. But I am having a hard time figuring out how to do it. To JIT compile C++ code, we do basically as follows: 1. call Driver::BuildCompilation(), which returns a

...portant for our target applications. > > Thanks, > - Dima. > > $ cat test.ll > ; ModuleID = '__kernelgen_main_module' > target datalayout = > "e-p:64:64:64-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-v16:16:16-v32:32:32-v64:64:64-v128:128:128-n16:32:64" > target triple = "nvptx64-unknown-unknown" > > @yweek.1533 = internal global [7 x [3 x i8]] [[3 x i8] c"MON", [3 x > i8] c"TUE", [3 x i8] c"WED", [3 x i8] c"THU", [3 x i8] c"FRI", [3 x > i8] c"SAT", [3...

Thanks for the heads up Philip ! I did come across a strange case where LLVM allowed "%" to be a part of a function's name. This was in the context of my patch https://reviews.llvm.org/D33985, where I prefix the name of the source function and the Scop ( A special kind of Region that Polly can optimize, the name of the Scop is the name of the Region ) to the name of the PTX kernel

...ate seems broken, > > and should be doing the right thing on most of your testcases. > > > > Let's take nary-add.ll, left_reassociate > > > > ; RUN: opt < %s -nary-reassociate -S | FileCheck %s > > > > target datalayout = "e-i64:64-v16:16-v32:32-n16:32:64" > > > > declare void @foo(i32) > > > > ; foo(a + c); > > ; foo((a + (b + c)); > > ; => > > ; t = a + c; > > ; foo(t); > > ; foo(t + b); > > define void @left_reassociate(i32 %a, i32 %b, i32 %c) { > > %1 = add i32 %...

...hanks, >>> - Dima. >>> >>> $ cat test.ll >>> ; ModuleID = '__kernelgen_main_module' >>> target datalayout = >>> "e-p:64:64:64-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-v16:16:16-v32:32:32-v64:64:64-v128:128:128-n16:32:64" >>> target triple = "nvptx64-unknown-unknown" >>> >>> @yweek.1533 = internal global [7 x [3 x i8]] [[3 x i8] c"MON", [3 x >>> i8] c"TUE", [3 x i8] c"WED", [3 x i8] c"THU", [3 x i8] c"FRI", [3...

With pleasure we announce the release of tinc version 1.1pre11. Here is a summary of the changes: * Added a "network" command to list or switch networks. * Switched to Ed25519 keys and the ChaCha-Poly1305 cipher for the new protocol. * AutoConnect is now a boolean option, when enabled tinc always tries to keep at least three meta-connections open. * The new protocol now

With pleasure we announce the release of tinc version 1.1pre11. Here is a summary of the changes: * Added a "network" command to list or switch networks. * Switched to Ed25519 keys and the ChaCha-Poly1305 cipher for the new protocol. * AutoConnect is now a boolean option, when enabled tinc always tries to keep at least three meta-connections open. * The new protocol now