search for: int8

Hello r users, I have to deal with int8 data with R. AFAIK R does only handle int4 with `as.integer` function [1]. I wonder: 1. what is the better approach to handle int8 ? `as.character` ? `as.numeric` ? 2. is there any plan to handle int8 in the future ? As you might know, int4 is to small to deal with earth population right now. Tha...

...If not, what sort of > calculations do you plan on doing with them? > Bill Dunlap > TIBCO Software > wdunlap tibco.com > > > On Fri, Jan 20, 2017 at 6:33 AM, Nicolas Paris <nicolas.paris at aphp.fr> wrote: > > Hello r users, > > > > I have to deal with int8 data with R. AFAIK R does only handle int4 > > with `as.integer` function [1]. I wonder: > > 1. what is the better approach to handle int8 ? `as.character` ? > > `as.numeric` ? > > 2. is there any plan to handle int8 in the future ? As you might know, > > int4 is to s...

...: int64 and bit64. You may need to find archival versions of these packages if they've fallen off cran. Murray (mobile phone) On Jan 20, 2017 7:20 AM, "Gabriel Becker" <gmbecker at ucdavis.edu> wrote: I am not on R-core, so cannot speak to future plans to internally support int8 (though my impression is that there aren't any, at least none that are close to fruition). The standard way of dealing with whole numbers too big to fit in an integer is to put them in a numeric (double down in C land). this can represent integers up to 2^53 without loss of precision see ( htt...

...hival versions of these packages if they've fallen off > cran. > > Murray (mobile phone) > > On Jan 20, 2017 7:20 AM, "Gabriel Becker" <gmbecker at ucdavis.edu> wrote: > > I am not on R-core, so cannot speak to future plans to internally support > int8 (though my impression is that there aren't any, at least none that are > close to fruition). > > The standard way of dealing with whole numbers too big to fit in an integer > is to put them in a numeric (double down in C land). this can represent > integers up to...

I am not on R-core, so cannot speak to future plans to internally support int8 (though my impression is that there aren't any, at least none that are close to fruition). The standard way of dealing with whole numbers too big to fit in an integer is to put them in a numeric (double down in C land). this can represent integers up to 2^53 without loss of precision see ( htt...

...t; > > > Murray (mobile phone) > > > > On Jan 20, 2017 7:20 AM, "Gabriel Becker" <gmbecker at ucdavis.edu> wrote: > > > > I am not on R-core, so cannot speak to future plans to internally > support > > int8 (though my impression is that there aren't any, at least none > that are > > close to fruition). > > > > The standard way of dealing with whole numbers too big to fit in an > integer > > is to put them in a numeric (double down i...

...phone) > > > > > > On Jan 20, 2017 7:20 AM, "Gabriel Becker" <gmbecker at ucdavis.edu> > wrote: > > > > > > I am not on R-core, so cannot speak to future plans to > internally > > support > > > int8 (though my impression is that there aren't any, at least > none > > that are > > > close to fruition). > > > > > > The standard way of dealing with whole numbers too big to fit > in an > > integer > > > is...

...he bit64 package (and, I believe, the int64 package, but since that's been archived it's not worth considering. Hadley On Fri, Jan 20, 2017 at 9:19 AM, Gabriel Becker <gmbecker at ucdavis.edu> wrote: > I am not on R-core, so cannot speak to future plans to internally support > int8 (though my impression is that there aren't any, at least none that are > close to fruition). > > The standard way of dealing with whole numbers too big to fit in an integer > is to put them in a numeric (double down in C land). this can represent > integers up to 2^53 without los...

...gt; > > On Jan 20, 2017 7:20 AM, "Gabriel Becker" <gmbecker at ucdavis.edu> > wrote: > > > > > > I am not on R-core, so cannot speak to future plans to > internally > > support > > > int8 (though my impression is that there aren't any, at least > none > > that are > > > close to fruition). > > > > > > The standard way of dealing with whole numbers too big to fit > in an > > integ...

Playing around with calling conventions naked functions and epilogue/prologue... Is it possible/expressible/feasible to alter the return address the function will return to? For example, when a function may return an Int8 or a Float64, depending on some external state (user, or random variable), instead of checking the returned type in the calling function, is it possible to pass 2 potential return addresses one suitable for Int8 and one suitable for Float64 and let the function return to the right place? if it is...

...anguage reference http://llvm.org/docs/LangRef.html , and understand the expressivity of aggregate types. What I do not yet have a good feeling for is when to use them. To give a concrete example, I'd like to parse a greyscale image in to an LLVM data structure. At each {x,y} point, there is an Int8 value between 0 and 255. Take a small 4x3 image. I could feed my pixels in to a flat Int8 vector of length 12. I could also feed it in to an array of length 4, of Int8 arrays of length 3. Now take 2 simple functions: one does greyscale brightening, the other does a sobel filter. The first needs on...

On 08/26/2011 05:32, Stephan Falke wrote: > As stated in LLVM's language reference manual > (http://llvm.org/docs/LangRef.html#i_shl), both arguments for a shl need > to have the same type. In my case, original types were uint8 (value) and uint32 (shift) llvm lacks unsigned types which made it S1=i8 and S2=i32. It's technically nothing wrong with such combination, and code works fine until I ran debug llvm for some other reason and this assert showed up. So if I need to shift signed int8 with unsigned uint32, I hav...

..._gcc42_objdir/i686-apple-darwin9/./libgfortran/.libs -L/sw/src/fink.build/llvm-gcc42-2.4-1/llvm_gcc42_objdir/i686-apple-darwin9/./libiberty -lm -o ./array_constructor_12.exe (timeout = 300) Unhandled expression! TREE_CODE: 68 <floor_div_expr 0x41765f60 type <integer_type 0x4170a4d0 int8 public DI size <integer_cst 0x41704930 constant invariant 64> unit size <integer_cst 0x41704960 constant invariant 8> align 64 symtab 12 alias set -1 precision 64 min <integer_cst 0x417048a0 -9223372036854775808> max <integer_cst 0x417048d0 9223372036854...

...this is that, by changing the member (that should be a > structure) to an array, the alignment is lost. As LLVM types don't I don't completely understand what you're saying here. Are you saying you want to have a J member of I repesented in LLVM, so that struct J becomes: { int32, int8, { int8 } } Do I understand you correctly? > So, I'm not proposing to have alignment in types nor to make LLVM > struct types conform to a specific ABI of a specific language, I'm > just saying that there should be a cleaner way... Very much like the > union type and bitfields...

...in a class. For example, let''s say I have a table called People: create table people ( id serial8 primary key ,name); which just holds a list of the people in the database. Then I have another table like this: create table log ( id serial8 primary key ,created_by int8 references people(id) ,created_for int8 references people(id) ); Now, in my Model class, how do I handle this? class Log < ActiveRecord::Base has_one :People end Is there some way to differentiate the two different has_one references but keep them looking at the same table? Thanks muc...

...ointer to an array element. I also understand that there is no 'address of' operation. As a result I can't figure out how to use constant derived types without assigning them to a global. Say I want to use the C bindings function LLVMValueRef LLVMConstString(char *, int, int) to get an int8* pointer to a C string constant - there doesn't seem to be any way to directly use the resulting [N x i8] value directly and there's no operator that gives me its address. The only way I can see to get a pointer to the string constant array is to go through a global variable, for example:...

On Sat, Nov 2, 2013 at 2:48 PM, Rob Stewart <robstewart57 at gmail.com> wrote: > Hi, I'm getting started with LLVM, with the intention of writing a DSL > that compiles to LLVM IR, to target a new CPU instruction set. I have > two questions: > > 1. Multimedia IO in LLVM > > In the paper "The LLVM Instruction Set and Compilation Strategy" [1], > there is

...rstand that there is no 'address of' operation. > > > > As a result I can't figure out how to use constant derived types without > > assigning them to a global. Say I want to use the C bindings function > > LLVMValueRef LLVMConstString(char *, int, int) to get an int8* pointer to > a > > C string constant - there doesn't seem to be any way to directly use the > > resulting [N x i8] value directly and there's no operator that gives me > its > > address. > > > > The only way I can see to get a pointer to the string const...

Hi, I'm getting started with LLVM, with the intention of writing a DSL that compiles to LLVM IR, to target a new CPU instruction set. I have two questions: 1. Multimedia IO in LLVM In the paper "The LLVM Instruction Set and Compilation Strategy" [1], there is talk about a possible multimedia instruction set in a future LLVM release: "Note that LLVM is a virtual instruction

Hi,    I would like to get the type of immediate value (integer) from MachineOperand Class. Currently the immediate value is being represented as int64_t. int64_t ImmVal; // For MO_Immediate.   Is it possible to find out whether the immediate value is int8, 16, 32 etc?   Note: My target has a virtual Instruction set.   Thanks in advance, -Sanjay -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090123/9071a954/attachment.html>