5 Коммитов

Автор	SHA1	Сообщение	Дата
Mike Hommey	eab43e4a6c	Bug 1413475 - Run clang-format on all files in memory/build/. r=njn ... --HG-- extra : rebase_source : a0a7ebff22c2387389d2f1dc75f8a5084f76ebb7	2017-11-01 17:20:54 +09:00
Mike Hommey	af14262e54	Bug 1413475 - Change comments to use C++ style // instead of /* */ in memory/build/. r=njn ... --HG-- extra : rebase_source : 8d8b85e8123f414cb1e0e1eb067e0d198b3ebb8f	2017-11-01 17:15:12 +09:00
Mike Hommey	1de1ed32d0	Bug 1413475 - Normalize license boilerplates in memory/build/. r=njn ... --HG-- extra : rebase_source : 9689f766211fbe1476c5e6d4774f1e95bb8e0208	2017-11-01 16:56:27 +09:00
Mike Hommey	f3bff41d59	Bug 1400096 - Don't define the operator new/delete functions as mangled in mozmem_wrap.cpp. r=njn ... Now that this is a C++ file, and that the function names are not mangled, we can just use the actual C++ names. We do however need to replace MOZ_MEMORY_API, which implies extern "C", with MFBT_API. Also use the correct type for the size given to operator new. It happened to work before because the generated code would just jump to malloc without touching any register, but on aarch64, unsigned int was the wrong type. --HG-- extra : rebase_source : 8045f30e9c609dd7d922c77d85ac017638df6961	2017-09-15 10:28:33 +09:00
Mike Hommey	9741c8e076	Bug 1400096 - Build mozmemory_wrap as C++. r=njn ... And since the build system doesn't handle transitions from foo.c to foo.cpp properly without a clobber, we work around the issue by switching to unified sources. --HG-- rename : memory/build/mozmemory_wrap.c => memory/build/mozmemory_wrap.cpp extra : rebase_source : 3f074b4ccab255bb0eb16841f79582060fafbc86	2017-09-15 10:19:37 +09:00