| d23d8d1d980bfd7afac9ec4bae7607bd65866fe6 |
|
06-Jan-2018 |
Mike Reed <reed@google.com> |
remove guarded old malloc code
Bug: skia:
Change-Id: I045e3816f04accebffd86c4aaaa5da67f198186c
Reviewed-on: https://skia-review.googlesource.com/91405
Reviewed-by: Florin Malita <fmalita@chromium.org>
Commit-Queue: Mike Reed <reed@google.com>
/external/skia/src/ports/SkMemory_mozalloc.cpp
|
| 8dc8dbc8211e7b0245a6e7db911265efbe0fccaf |
|
05-Jan-2018 |
Mike Reed <reed@google.com> |
begin cleanup of malloc porting layer
1. Merge some of the allocators into sk_malloc_flags by redefining a flag to mean zero-init
2. Add more private helpers to simplify our call-sites (and handle some overflow mul checks)
3. The 2-param helpers rely on the saturating SkSafeMath::Mul to pass max_size_t as the request,
which should always fail.
Bug:508641
Change-Id: I322f1e6ed91113467e0fdb12c91c3dad33d890c8
Reviewed-on: https://skia-review.googlesource.com/90940
Commit-Queue: Mike Reed <reed@google.com>
Reviewed-by: Robert Phillips <robertphillips@google.com>
Reviewed-by: Stephan Altmueller <stephana@google.com>
/external/skia/src/ports/SkMemory_mozalloc.cpp
|
| b549cc38c8404c58642ada75c0b24907702cc005 |
|
27-Mar-2017 |
Herb Derby <herb@google.com> |
Change SkMemory to the more accurately named SkMalloc.
Change-Id: I6b08a74234b99bac866bad71014b94f7ec2d4bc8
Reviewed-on: https://skia-review.googlesource.com/10188
Commit-Queue: Herb Derby <herb@google.com>
Reviewed-by: Brian Salomon <bsalomon@google.com>
/external/skia/src/ports/SkMemory_mozalloc.cpp
|
| d7b34a5ca0a9183e70737125c688d2a8b5310d81 |
|
20-Mar-2017 |
Herb Derby <herb@google.com> |
Make SkMemory.h and adjust all files for usage.
This will be rolled out in three stages:
1) make SkMemory.h and have SkTypes.h include it.
2) Adjust chromium and android.
3) no long include SkMemory.h in SkTypes.h
Change-Id: If360ef5e1164d88f50b03f279e2e963ca2f57d5d
Reviewed-on: https://skia-review.googlesource.com/9874
Reviewed-by: Brian Salomon <bsalomon@google.com>
Commit-Queue: Herb Derby <herb@google.com>
/external/skia/src/ports/SkMemory_mozalloc.cpp
|
| f2b340fc885ad2a12d2d73974eff9c8f4c94192c |
|
29-Jan-2016 |
djsollen <djsollen@google.com> |
Consolidate SK_CRASH and sk_throw into SK_ABORT
TBR=reed@google.com
GOLD_TRYBOT_URL= https://gold.skia.org/search2?unt=true&query=source_type%3Dgm&master=false&issue=1648343003
Review URL: https://codereview.chromium.org/1648343003
/external/skia/src/ports/SkMemory_mozalloc.cpp
|
| aa97a84404c7505738713a4c19b42347c7daef9e |
|
22-Jan-2016 |
djsollen <djsollen@google.com> |
Revert of Consolidate SK_CRASH and sk_throw into SK_ABORT (patchset #5 id:80001 of https://codereview.chromium.org/1610823002/ )
Reason for revert:
Chrome is calling SK_CRASH
Original issue's description:
> Consolidate SK_CRASH and sk_throw into SK_ABORT
> GOLD_TRYBOT_URL= https://gold.skia.org/search2?unt=true&query=source_type%3Dgm&master=false&issue=1610823002
>
> Committed: https://skia.googlesource.com/skia/+/4c5cd7d527ed29aabfa72aa47b23a4496eeda357
TBR=reed@google.com
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
Review URL: https://codereview.chromium.org/1620333002
/external/skia/src/ports/SkMemory_mozalloc.cpp
|
| 4c5cd7d527ed29aabfa72aa47b23a4496eeda357 |
|
22-Jan-2016 |
djsollen <djsollen@google.com> |
Consolidate SK_CRASH and sk_throw into SK_ABORT
GOLD_TRYBOT_URL= https://gold.skia.org/search2?unt=true&query=source_type%3Dgm&master=false&issue=1610823002
Review URL: https://codereview.chromium.org/1610823002
/external/skia/src/ports/SkMemory_mozalloc.cpp
|
| b8b479b29d24f45a25dca74752ff6ed653e60ba9 |
|
23-Nov-2015 |
lsalzman <lsalzman@mozilla.com> |
use malloc/calloc/free instead of moz_malloc/moz_calloc/moz_free in ports/SkMemory_mozalloc.cpp
BUG=skia:4560
Review URL: https://codereview.chromium.org/1449093002
/external/skia/src/ports/SkMemory_mozalloc.cpp
|
| 519f9677a41239808f41a7c13ef1f6e05eb1ed50 |
|
20-Sep-2013 |
mtklein@google.com <mtklein@google.com@2bbb7eff-a529-9590-31e7-b0007b416f81> |
Add sk_calloc. Remove SkMemory_stdlib, which seems unused.
I'm seeing basically no difference between malloc + bzero and calloc on my desktop, but on a Galaxy Nexus calloc is never slower, and significantly faster once the allocation size becomes large, both for allocation and for _reading_.
BUG=skia:1662
R=reed@google.com
Review URL: https://codereview.chromium.org/24251008
git-svn-id: http://skia.googlecode.com/svn/trunk@11414 2bbb7eff-a529-9590-31e7-b0007b416f81
/external/skia/src/ports/SkMemory_mozalloc.cpp
|
| e16efc1882ab34a0bb3ae361a2d37f840044cf87 |
|
26-Jan-2013 |
skia.committer@gmail.com <skia.committer@gmail.com@2bbb7eff-a529-9590-31e7-b0007b416f81> |
Sanitizing source files in Skia_Periodic_House_Keeping
git-svn-id: http://skia.googlecode.com/svn/trunk@7406 2bbb7eff-a529-9590-31e7-b0007b416f81
/external/skia/src/ports/SkMemory_mozalloc.cpp
|
| cb39ee645a32b7e15a813672ac0acfd7e8dc114b |
|
27-Aug-2012 |
george@mozilla.com <george@mozilla.com@2bbb7eff-a529-9590-31e7-b0007b416f81> |
Add a new SkMemory implementation that uses mozalloc instead of malloc
git-svn-id: http://skia.googlecode.com/svn/trunk@5292 2bbb7eff-a529-9590-31e7-b0007b416f81
/external/skia/src/ports/SkMemory_mozalloc.cpp
|