5
100%
master: 100%

Ran 16 Apr 2015 07:14PM UTC

Files 23

Run time 4s

Badge

Embed ▾

Committed 16 Apr 2015 07:03PM UTC coverage: 99.958% (-0.04%) from 100.0%

Job # CONF=debug ARCH=x86_64

Build Type

Pull #305

travis-ci

Committed by

pah

Commit Message

Avoid calling memcpy with NULL pointers

According to the C/C++ standards, calling `memcpy(NULL, NULL, 0)` is
undefined behaviour. Recent GCC versions may rely on this by optimizing
NULL pointer checks more aggressively, see [1].

This patch tries to avoid calling std::memcpy with zero elements.
As a side effect, explicitly return NULL when requesting an empty block
from MemoryPoolAllocator::Malloc.

This may be related to #301.

[1] https://gcc.gnu.org/gcc-4.9/porting_to.html

Pull Request Pull Request #305: Avoid calling memcpy with NULL pointers

Run Details

2357 of 2358 relevant lines covered (99.96%)

1330563.3 hits per line

miloyip / rapidjson / 757 / 5
100%
master: 100%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 757.5 (CONF=debug ARCH=x86_64)

miloyip / rapidjson / 757 / 5 100% master: 100%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 757.5 (CONF=debug ARCH=x86_64)

miloyip / rapidjson / 757 / 5
100%
master: 100%

README BADGES
x