search for: i288

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi devs, I'd like to ask for some advise about optimization passes. Which pass might be responsible for this LLVM IR and why? %0 = load i288* bitcast ([9 x i32]* @array to i288*), align 16 %1 = lshr i288 %0, 224 array is just a global constant array of 9 integers and the code only accesses individual elements. The LLVM version is 3.1. Thanks, Mario -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG w...

...rio Schwalbe Sent: Saturday, July 07, 2012 22:19 To: llvmdev at cs.uiuc.edu Subject: [LLVMdev] Large integers -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi devs, I'd like to ask for some advise about optimization passes. Which pass might be responsible for this LLVM IR and why? %0 = load i288* bitcast ([9 x i32]* @array to i288*), align 16 %1 = lshr i288 %0, 224 array is just a global constant array of 9 integers and the code only accesses individual elements. The LLVM version is 3.1. Thanks, Mario -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG w...

...but is more common there due to the next point. I've been told by Rafael Ávila de Espíndola that for this, I would need an Emscripten target in LLVM. Would that be upstreamable? (With or without Emscripten itself, preferably with?) 2. Optimization sometimes generates types like i288, which Emscripten currently doesn't handle. From an optimizing perspective, it isn't yet clear if it would be faster to try to directly implement those, or to just break them up into more manageable native (32-bit) sizes. Note that even i64 is somewhat challenging to implemen...

...was hoping that unless the code literally did something crazy like a load of an 8-byte value from a hardcoded 4-byte aligned address (like 0x4), then otherwise "normal" C/C++ code would always end up aligned. Is that correct? > > > 2. Optimization sometimes generates types like i288, which > >   Emscripten currently doesn't handle. From an optimizing > >   perspective, it isn't yet clear if it would be faster to > >   try to directly implement those, or to just break them up > >   into more manageable native (32-bit) sizes. Note that even > &...

...on the net, but I was not able to be sure of which packages I’ll need to perform the kriging (maybe geoR?) and then plot it in the area map. Is R able to do that? What packages I need to know to do so? I just need a starting point to go forward. I need to generate something like this: http://i288.photobucket.com/albums/ll162/Godrigos/Kriging.jpg (but without the top right area, just the different grayscale kriging area). library(xlsReadWrite) library(maps) library(mapdata) library(maptools) Pontos<-read.xls('Pontos.xls',sheet=1,rowNames=T) Prof<-read.xls('Pontos...

...itself, preferably >   with?) Adding a Emscripten target to clang would be fine. Note that clang might generate unaligned loads anyway, but specifying an appropriate target will ensure it doesn't use such loads unless they are necessary. > 2. Optimization sometimes generates types like i288, which >   Emscripten currently doesn't handle. From an optimizing >   perspective, it isn't yet clear if it would be faster to >   try to directly implement those, or to just break them up >   into more manageable native (32-bit) sizes. Note that even >   i64 is somewhat cha...

..."something crazy" (like using "__attribute__((packed))") occasionally, though. Also, the optimizer will sometimes turn a memcpy into an unaligned load+store, or a pair of small loads into an unaligned load. >> >> > 2. Optimization sometimes generates types like i288, which >> >   Emscripten currently doesn't handle. From an optimizing >> >   perspective, it isn't yet clear if it would be faster to >> >   try to directly implement those, or to just break them up >> >   into more manageable native (32-bit) sizes. Note...

...obool = icmp eq i32 %call6, 0 %lost. = select i1 %tobool, i32 %lost, i32 1 br label %if.end10 if.else: ; preds = %if.then3 %xi.addr.06.i287 = getelementptr inbounds i16* %s, i32 1 store i16 0, i16* %xi.addr.06.i287, align 2, !tbaa !5 %xi.addr.06.1.i288 = getelementptr inbounds i16* %s, i32 2 store i16 0, i16* %xi.addr.06.1.i288, align 2, !tbaa !5 %xi.addr.06.2.i289 = getelementptr inbounds i16* %s, i32 3 store i16 0, i16* %xi.addr.06.2.i289, align 2, !tbaa !5 %xi.addr.06.3.i290 = getelementptr inbounds i16* %s, i32 4 store i16 0, i16* %...