From cd051604b1b5f8555cf692b91d0105d7a7117feb Mon Sep 17 00:00:00 2001 From: Tom Sepez Date: Thu, 30 Apr 2015 15:21:18 -0700 Subject: Try to take advantage of unused bytes at end of CFX_ByteString. Given the representation of StringData, it seems sub-optimal not to be doing this. R=thestig@chromium.org Review URL: https://codereview.chromium.org/1120703003 --- core/src/fxcrt/fx_basic_bstring.cpp | 18 +++++++++++++++--- 1 file changed, 15 insertions(+), 3 deletions(-) (limited to 'core/src/fxcrt') diff --git a/core/src/fxcrt/fx_basic_bstring.cpp b/core/src/fxcrt/fx_basic_bstring.cpp index 961aebe69c..2c8f7a766b 100644 --- a/core/src/fxcrt/fx_basic_bstring.cpp +++ b/core/src/fxcrt/fx_basic_bstring.cpp @@ -52,13 +52,25 @@ static CFX_StringData* FX_AllocString(int nLen) if (nLen == 0 || nLen < 0) { return NULL; } + + int overhead = sizeof(long) * 3 + 1; // 3 longs in header plus 1 for NUL. pdfium::base::CheckedNumeric nSize = nLen; - nSize += sizeof(long) * 3 + 1; - CFX_StringData* pData = (CFX_StringData*)FX_Alloc(FX_BYTE, nSize.ValueOrDie()); + nSize += overhead; + + // Now round to an 8-byte boundary. We'd expect that this is the minimum + // granularity of any of the underlying allocators, so there may be cases + // where we can save a re-alloc when adding a few characters to a string + // by using this otherwise wasted space. + nSize += 7; + int totalSize = nSize.ValueOrDie() & ~7; + int usableSize = totalSize - overhead; + FXSYS_assert(usableSize >= nLen); + + CFX_StringData* pData = (CFX_StringData*)FX_Alloc(FX_BYTE, totalSize); if (!pData) { return NULL; } - pData->m_nAllocLength = nLen; + pData->m_nAllocLength = usableSize; pData->m_nDataLength = nLen; pData->m_nRefs = 1; pData->m_String[nLen] = 0; -- cgit v1.2.3