On 22/01/2012 13:56, Prof Brian Ripley wrote:
This has languished for a long time, and we should make a decision
before FF for 2.15.0.
It seems to me that in so far as there is a problem, it is that we
serialize via XDR, and that since that was invented little-endian CPUs
have taken over the
This has languished for a long time, and we should make a decision
before FF for 2.15.0.
It seems to me that in so far as there is a problem, it is that we
serialize via XDR, and that since that was invented little-endian CPUs
have taken over the world. So for the only cases I can imagine
Has there been any movement on this patch? It will improve the
serialize/unserialize performance.
Thanks,
--Michael
On Mon, Oct 3, 2011 at 9:28 AM, luke-tier...@uiowa.edu wrote:
It's on my list to look at but I may not get to it for a couple of
weeks. Someone else may get there earlier.
Not yet . It overlaps with some other work and will be done in due course.
luke
On Mon, 5 Dec 2011, Michael Spiegel wrote:
Has there been any movement on this patch? It will improve the
serialize/unserialize performance.
Thanks,
--Michael
On Mon, Oct 3, 2011 at 9:28 AM,
Any thoughts? I haven't heard any feedback on this patch.
Thanks!
--Michael
On Wed, Sep 28, 2011 at 3:10 PM, Michael Spiegel
michael.m.spie...@gmail.com wrote:
Hi folks,
I've attached a patch to the svn trunk that improves the performance
of the serialize/unserialize interface for vector
It's on my list to look at but I may not get to it for a couple of
weeks. Someone else may get there earlier.
Best,
luke
On Mon, 3 Oct 2011, Michael Spiegel wrote:
Any thoughts? I haven't heard any feedback on this patch.
Thanks!
--Michael
On Wed, Sep 28, 2011 at 3:10 PM, Michael Spiegel
Hi folks,
I've attached a patch to the svn trunk that improves the performance
of the serialize/unserialize interface for vector types. The current
implementation: a) invokes the R_XDREncode operation for each element
of the vector type, and b) uses a switch statement to determine the
stream type
