Please report new issues athttps://github.com/DOCGroup
he CDR streaming classes compute the alignment on each operation, but they could remember the alingment from the previous insertion or extraction operation; saving a few cycles but spending a little more memory.
This is a valid enhacement request, i'm marking it as accepted but their implementation is deferred
This bug was an enhacement request originally, but must be upgraded to a real bug report. Here is the long explanation: - Consider a CDR encapsulation, they are marshaled as a sequence of octets into the containing CDR stream. If the sequence is long enough TAO will avoid a data copy and simply chain the octet sequence as another element into the message block chain of the containing CDR stream. - Now look at the overall alignment of the containing CDR stream, the first block on the stream starts properly aligned in memory, so its internal alignment and its memory alignment match. The same situation is true for the contained CDR encapsulation. But the CDR encapsulation may end on an 8-byte boundary in memory, while it is a 4 byte-boundary wrt to the start of the containing stream. To put numbers to this example, consider an encapsulation of 16 bytes, it would start and end on an 8-byte boundary. Assume the containing stream has 32 bytes so far, after inserting the encapsulation length the stream will contain 36 bytes, a 4-byte boundary. After adding the 16 bytes of the CDR stream it should also end on a 4-byte boundary, but because the message blocks are only chained, and the contained stream is properly aligned in memory things don't work right. Naturally the numbers have to be much larger for the optimizations to kick in, but the same ideas apply. Many thanks to Dennis Noll for tracking this down.
The real bug has been fixed, look into this ChangeLog entry for details: Tue Feb 29 16:40:43 2000 Carlos O'Ryan <coryan@uci.edu> What remains is to optimize the InputCDR stream, but i won't be able to work in that for a long time, back to the common pool.
Please assign . . .
This is just a reminder for future optimizations.
Accept, to be addressed later.