x86-64

Trying to install cassandra on linux from latest stable release - http://cassandra.apache.org/download/ - 1.2.6 I have modified the cassndra.yaml to point to a custom directory instead of /var since I do not have write access on /var I am seeing this error on startup. Not able to find any answers on google yet since the release seems relatively new. Just posting it here in case its a silly mistake on my side. Same distribution file worked fine on my macos x86_64 machine. INFO 19:24:35,513 Not using multi-threaded compaction java.lang.reflect.InvocationTargetException at sun.reflect

We're building a hybrid app with IBM Mobile First Platform (7.0) for iOS and Android platforms. We're using JSONStore to save user non-confidential data (we're not cyphering the data stored). When we deploy the application to a Samsung Galaxy S6 (Model SM-G920I) we're having this error on the init method of the Json Store: Error code: -11 OPERATION_FAILED_ON_SPECIFIC_DOCUMENT IBM Mobile First Platform - JSONStore errors Error details : "dlopen failed: "/data/data/com.MyMobileApp/files/libcrypto.so.1.0.0" is 32-bit instead of 64-bit" Making some research, we cannot figure out something else

While learning x86-64 assembly, I came across my first incompatibility between Intel 64 and AMD64 implementations of "x86-64": Why does syscall compile in NASM 32 bit output while popa does not compile in 64 bit? syscall is valid in the compatibility mode of one but not the other. Is there a better way of finding out those incompatibilities besides carefully reading both manuals and comparing them, which is error prone and duplicates my manual reading effort when aiming for portability? For example, it would be much easier if there was either: a standard subset which both Intel and AMD claim

The 64-bit Windows ABI defines a generalized exception handling mechanism , which I believe is shared across C++ exceptions and structured exceptions available even in other languages such as C. If I'm writing an x86-64 assembly routine to be compiled in nasm and linked into a C or C++ library, what accommodations do I need make on Windows in terms of generating unwind info and so on? I'm not planning on generating any exceptions directly in the assembly code, although I suppose it is possible that the code may get an access violation if a user-supplied buffer is invalid, etc. I'd like the

SHLD/SHRD instructions are assembly instructions to implement multiprecisions shifts. Consider the following problem: uint64_t array[4] = {/*something*/}; left_shift(array, 172); right_shift(array, 172); What is the most efficient way to implement left_shift and right_shift , two functions that operates a shift on an array of four 64-bit unsigned integer as if it was a big 256 bits unsigned integer? Is the most efficient way of doing that is by using SHLD/SHRD instructions, or is there better (like SIMD versions) instructions on modern architecture? In this answer I'm only going to talk about

Profiling suggests that this function here is a real bottle neck for my application: static inline int countEqualChars(const char* string1, const char* string2, int size) { int r = 0; for (int j = 0; j < size; ++j) { if (string1[j] == string2[j]) { ++r; } } return r; } Even with -O3 and -march=native , G++ 4.7.2 does not vectorize this function (I checked the assembler output). Now, I'm not an expert with SSE and friends, but I think that comparing more than one character at once should be faster. Any ideas on how to speed things up? Target architecture is x86-64. Sam Compiler flags for