Displaying 6 results from an estimated 6 matches for "protocolbuff".
2009 Nov 07
1
getConnection, R_outpstream_st
Hello,
I'm trying to use the limited connections api defined in Rinternals.h. I
have code that looks like this (inspired from do_serializeToConn) :
SEXP serialize_to_connection( SEXP xp, SEXP connection ){
Rconnection con ;
struct R_outpstream_st out;
R_pstream_format_t type = R_pstream_binary_format ;
SEXP (*hook)(SEXP, SEXP) = NULL ;
con = getConnection(Rf_asInteger(connection));
2008 Sep 25
0
Protocol Buffers in Compiz and libcompizconfig
Hi,
We're planning to use Protocol Buffers (Google's data interchange
format: http://code.google.com/apis/protocolbuffers/ ) in a future
version of Compiz and libcompizconfig to speed up metadata parsing,
which currently makes up more than 75% of the start-up time for Compiz
according to Valgrind. Preliminary work in this direction has shown
promising results.
We'll be adding libprotobuf as an optional depende...
2009 Sep 11
0
ANN: rproto v1 (Protocol Buffers and R)
...to file can be found in the source.
Todo:
Very possible though needs some reading on my part: it is possible to
extend this to serialize functions, expressions, environments and
several other objects.
However that is some time in the future.
Regards
Saptarshi
[1] http://code.google.com/apis/protocolbuffers/docs/overview.html
Download:
http://ml.stat.purdue.edu/rproto_1.0.tar.gz
Saptarshi Guha | saptarshi.guha@gmail.com | http://www.stat.purdue.edu/~sguha
[[alternative HTML version deleted]]
2009 Sep 11
0
ANN: rproto v1 (Protocol Buffers and R) [repost]
...proto file can be found in the source.
Todo:
Very possible though needs some reading on my part: it is possible to
extend this to serialize functions, expressions, environments and
several other objects.
However that is some time in the future.
Regards
Saptarshi
[1] http://code.google.com/apis/protocolbuffers/docs/overview.html
Download:
http://ml.stat.purdue.edu/rproto_1.0.tar.gz
2020 May 26
2
Emitting aligned nlist_64 structures for Mach-O in MC
I looked into this further. ld64 has a macho_nlist abstraction over the various underlying nlist structures [1]. On x86-64, the P::getP referenced in n_value will resolve to [2], which in turn goes to [3], which calls OSReadLittleInt64. On a little endian machine, OSReadLittleEndian just calls _OSReadInt64 [4], which in turn does a pointer arithmetic and cast and then dereferences the pointer [5].
2018 Nov 14
2
Building LLVM with VisualStudio 2017
Hey Bjorn,
Were you able to figure this out or is it still broken for you?
Our scenario is a little bit different, but I have a theory as to what may be going wrong. What linker are you using when you compile your project with clang-cl? I am wondering whether the version of the linker and/or the libraries that you are using is too old in comparison to the one used for the clang compilation.