search for: intn

Hello, I have a function for reading a data-frame from a file, which contains E = read.table(file = filename, header = T, colClasses = c(rep("integer",6),"numeric","integer",rep("numeric",8)), ...) Now a small variation arose, where colClasses =

On Apr 2, 2010, at 9:28 AM, 琬菁楊 wrote: > Hello Chris, > > I have survey the efi specification and ask some question to efi engineer. > Difference between EFI C and ANSI C is as following: > 1. void* > In EFI C, the void* is 4-byte for 32-bit processor and 8-byte for 64-bit processor. > And it can appears in any where like ANSI C. > So the main problem is that

...tion length. - Renames hvm_inject_exception to hvm_inject_trap. Then define a couple of wrappers around that function for existing callers, so that their parameter lists actually *shrink*. This series of patches fix the mistake for debug exception(#DB), overflow exception(#OF) and INT3(#BP), INTn instruction emulation. PATCH 3 and PATCH 4 supply an interface for userspace to inject trap. PATCH 1: Define new struct hvm_trap and cleanup vmx exception. PATCH 2: Fix the mistake for debug exception(#DB), overflow exception(#OF) and INT3(#BP), INTn instruction emulation. Add inslen field in...

Hello Chris, I have survey the efi specification and ask some question to efi engineer. Difference between EFI C and ANSI C is as following: 1. void* In EFI C, the void* is 4-byte for 32-bit processor and 8-byte for 64-bit processor. And it can appears in any where like ANSI C. So the main problem is that struct layout like struct S{ void* X; }; is not static. 2.

Fix the mistake for debug exception(#DB), overflow exception(#OF; generated by INTO) and int 3(#BP) instruction emulation. For INTn (CD ib), it should use type 4 (software interrupt). For INT3 (CC; NOT CD ib with ib=3) and INTO (CE; NOT CD ib with ib=4), it should use type 6 (software exception). For other exceptions (#DE, #DB, #BR, #UD, #NM, #TS, #NP, #SS, #GP, #PF, #MF, #AC, #MC, and #XM), it should use type 3 (hardware exc...

Hi all, After searching for a decent compiler backend for ages (google sometimes isn't helpful), I recently stumbled upon LLVM. Woot!! I work on bignum arithmetic (I'm a professional mathematician) and have recently decided to switch from developing GPL'd bignum code to BSD licensed code. (See http://www.mpir.org/ which I contributed to for a while - a fork of GMP). Please bear with

...I am interested to know what the existing intentions > of the LLVM devs are for supporting arbitrary precision stuff, as it > seemed, at least at first blush, as though something non-trivial may > have been planned all along. > > It interested me greatly when I noticed you had these intn types for > an arbitrary number of bits, and it almost made me think there was > some planning had gone into supporting arbitrary precision arithmetic > as basic instructions in the LLVM. Bizarre, but not stupid, perhaps. There really isn't any grand plan here; LLVM switched a while b...

...know what the existing intentions >> of the LLVM devs are for supporting arbitrary precision stuff, as it >> seemed, at least at first blush, as though something non-trivial may >> have been planned all along. >> >> It interested me greatly when I noticed you had these intn types for >> an arbitrary number of bits, and it almost made me think there was >> some planning had gone into supporting arbitrary precision arithmetic >> as basic instructions in the LLVM. Bizarre, but not stupid, perhaps. > > There really isn't any grand plan here; LL...

This series of patches fix the mistake for debug exception(#DB), overflow exception(#OF) and INT3(#BP), INTn instruction emulation. Introduce new function vmx_inject_sw_exception() which deliver the software excetion, software interrupt and privileged software exception. Split hardware exception as a seperate function(old function vmx_inject_hw_exception()). Also Passed down intruction length to except...

Thanks Nick. I've been pursuing Gao's technique but can't seem to get opt to remove obviously dead code from even the following trivial example: int mult(int a, int b){ return a*b; } int main(void){ return 0; } While mult is never called it still is not removed. I just can't seem to get opt to understand it's seeing the whole program so it can remove this

Hello, I recently came across an OpenCL kernel in which an int vector type was subtracted from the INT_MIN constant, e.g. int2 v2 = INT_MIN - (int2)(0); INT_MIN was defined as #define INT_MIN (-2147483648) Clang in OpenCL modes (-x cl) produces the following error: vector_conversion.c:12:42: error: can't convert between vector values of different size ('long' and 'int2'

...to output [type Object] for numbers diff --git a/libswfdec/js/jsnum.c b/libswfdec/js/jsnum.c index 1e92a7a..d9063f4 100644 --- a/libswfdec/js/jsnum.c +++ b/libswfdec/js/jsnum.c @@ -249,6 +249,15 @@ IntToString(jsint i, char *buf, size_t b static JSBool num_toString(JSContext *cx, JSObject *obj, uintN argc, jsval *argv, jsval *rval) { + JSString *string; + + string = JS_InternString (cx, "[type Object]"); + if (string == NULL) + return JS_FALSE; + + *rval = STRING_TO_JSVAL (string); + return JS_TRUE; +#if 0 jsval v; jsdouble d; jsint base; @@ -286,6 +295,7 @@ nu...