search for: bytebuffer

...I I thought I''d share: require ''java'' # LoadLibrary() Kernel32 = com.sun.jna.NativeLibrary.getInstance("kernel32") # GetProcAddress() GetCurrentDirectoryA = Kernel32.getFunction(''GetCurrentDirectoryA'') # You can also do -> buf = java.nio.ByteBuffer.allocate(256) buf = Array.new(256).to_java(:byte) GetCurrentDirectoryA.invokeInt([256, buf].to_java) buf = java.lang.String.new(buf) p buf.to_s.strip It''s a little clunkier than MRI at the moment, because Java strings are immutable. We''re passing by reference, so we have to pas...

Hello All, I had been trying to work on Rails 4 and Mongoid gem. The following are the versions I had installed: bson-2.2.1 mongoid-3.1.6 After installing and trying to run "rails generate" command. It is failing with NameSpace error for BSON::ByteBuffer. It is trying to connect to mongodb server initially and getting successful. Post that it is failing with the following error >rails generate C:/Ruby193/lib/ruby/gems/1.9.1/gems/mongo-1.9.2/lib/mongo/cursor.rb:585:in `construct_query_message': uninitialized constant BSON::ByteBuffer (Name...

My idea was to create a complete backend treating Java as a normal platform, to enable LLVM to compile programs to Java Bytecode (.class) and Java Archive files (.jar). This could be useful in situations where we need to compile a program for a platform still not natively supported by LLVM. I don't know if it exists already, I've heard about this "LLJVM" but I don't think it

...h a "\0" to be a byte buffer # and convert it automatically. This is necessary because Java # strings are immutable. args.each_with_index do |arg, i| if arg.is_a?(String) && arg[0,1] == "\0" args[i, 1] = java.nio.ByteBuffer.allocate(arg.length) end end args = [*args].to_java # Call the proper JNA invocation based on the return type case @return_type when ''P'' rv = @func.invokePointer(args) when ''L...

I work with problems that have rather large data requirements -- typically a bunch of multigig arrays. Given how generous R is with using memory, the only way for me to work with R has been to use bigmatrices from bigmemory package. One thing that is missing a bit is interoperability of bigmatrices with C++ and possibly java. What i mean by that is API that would allow read and write filebacked

...is not. There is no equivalent of inttoptr or ptrtoint in Java bytecode and the closest equivalent of a GEP is to retrieve a field from an object (though that’s only really for GEP + load/store). > > You could potentially do something a bit ugly and treat all of LLVM memory as one big ByteBuffer object, and make pointers indexes into this, but then you’d make it very hard for your LLVM-originating code to interoperate with Java-originating code and so you’d have to write a lot of code to take the place of the system call layer. The caveat here is that Java has this "private"...

...lass file 'java/lang/RuntimeException' requires Java version 1.7. This JVM only supports Java versions up to 1.6. WARNING: Class file 'java/lang/IllegalAccessException' requires Java version 1.7. This JVM only supports Java versions up to 1.6. WARNING: Class file 'java/nio/DirectByteBuffer' requires Java version 1.7. This JVM only supports Java versions up to 1.6. WARNING: Class file 'java/nio/MappedByteBuffer' requires Java version 1.7. This JVM only supports Java versions up to 1.6. WARNING: Class file 'java/nio/ByteBuffer' requires Java version 1.7. This JVM on...

...ption' requires Java version >> 1.7. This JVM only supports Java versions up to 1.6. >> WARNING: Class file 'java/lang/IllegalAccessException' requires Java >> version 1.7. This JVM only supports Java versions up to 1.6. >> WARNING: Class file 'java/nio/DirectByteBuffer' requires Java version >> 1.7. This JVM only supports Java versions up to 1.6. >> WARNING: Class file 'java/nio/MappedByteBuffer' requires Java version >> 1.7. This JVM only supports Java versions up to 1.6. >> WARNING: Class file 'java/nio/ByteBuffer' re...

...lang/RuntimeException' requires Java version > 1.7. This JVM only supports Java versions up to 1.6. > WARNING: Class file 'java/lang/IllegalAccessException' requires Java > version 1.7. This JVM only supports Java versions up to 1.6. > WARNING: Class file 'java/nio/DirectByteBuffer' requires Java version > 1.7. This JVM only supports Java versions up to 1.6. > WARNING: Class file 'java/nio/MappedByteBuffer' requires Java version > 1.7. This JVM only supports Java versions up to 1.6. > WARNING: Class file 'java/nio/ByteBuffer' requires Java vers...

...res Java version >>> 1.7. This JVM only supports Java versions up to 1.6. >>> WARNING: Class file 'java/lang/IllegalAccessException' requires Java >>> version 1.7. This JVM only supports Java versions up to 1.6. >>> WARNING: Class file 'java/nio/DirectByteBuffer' requires Java version >>> 1.7. This JVM only supports Java versions up to 1.6. >>> WARNING: Class file 'java/nio/MappedByteBuffer' requires Java version >>> 1.7. This JVM only supports Java versions up to 1.6. >>> WARNING: Class file 'java/nio/By...

I also misunderstood :) So, in this case, the problem is that your version of openjdk is probably not supported. In fact, we only support the version 7u23 of openjdk :) You can find this version here: http://www.oracle.com/technetwork/java/javase/downloads/java-archive-downloads-javase7-521261.html#jdk-7u25-oth-JPR Currently, I'm modifying the internal design of vmkit and I'm not working

This may not be a ZFS issue, so please bear with me! I have 4 internal drives that I have striped/mirrored with ZFS and have an application server which is reading/writing to hundreds of thousands of files on it, thousands of files @ a time. If 1 client uses the app server, the transaction (reading/writing to ~80 files) takes about 200 ms. If I have about 80 clients attempting it @ once, it can

I guess I mispoke, I checked out the source from http://llvm.org/svn/llvm-project/vmkit/trunk. I thought this was vmkit2. I guess I was just referring to vmkit then. On Thu, Nov 21, 2013 at 12:10 PM, Gaël Thomas <gael.thomas00 at gmail.com> wrote: > Hi Adam, > > I don't know which repo you have used? Because only the llvm repo is > maintained (not the gforge one), and