Commit graph

21 commits

Author SHA1 Message Date
athenian200
b652dd59ae MoonchildProductions#1251 - Part 7: All the posix_m* memory-related stuff, gathered together.
https://bugzilla.mozilla.org/show_bug.cgi?id=1158445
https://bugzilla.mozilla.org/show_bug.cgi?id=963983
https://bugzilla.mozilla.org/show_bug.cgi?id=1542758

Solaris madvise and malign don't perfectly map to their POSIX counterparts, and some Linux versions (especially Android) don't define the POSIX counterparts at all, so options are limited. Ideally posix_madvise and posix_malign should be the safer and more portable options for all platforms.
2019-11-04 11:52:22 +08:00
athenian200
6de8a0f12d MoonchildProductions#1251 - Part 1: Restore initial Solaris support, fixed up.
Compared with what Pale Moon had for Solaris originally, this is mostly the same zero point I started patching from, but I've made the following changes here after reviewing all this initial code I never looked at closely before.

1. In package-manifest.in for both Basilisk and Pale Moon, I've made the SPARC code for libfreebl not interefere with the x86 code, use the proper build flags, and also updated it to allow a SPARC64 build which is more likely to be used than the 32-bit SPARC code we had there.

2. See Mozilla bug #832272 and the old rules.mk patch from around Firefox 30 in oracle/solaris-userland. I believe they screwed up NSINSTALL on Solaris when they were trying to streamline the NSS buildsystem, because they started having unexplained issues with it around that time after Firefox 22 that they never properly resolved until Mozilla began building NSS with gyp files. I'm actually not even sure how relevant the thing they broke actually is to Solaris at this point, bug 665509 is so old it predates Firefox itself and goes back to the Mozilla suite days. I believe $(INSTALL) -t was wrong, and they meant $(NSINSTALL) -t because that makes more sense and is closer to what was there originally. It's what they have for WINNT, and it's possible a fix more like that could serve for Solaris as well. Alternatively, we could get rid of all these half-broken Makefiles and start building NSS with gyp files like Mozilla did.

3. I've completely cut out support for the Sun compiler and taken into account the reality that everyone builds Firefox (and therefore its forks) with GCC now on Solaris. This alone helped clean up a lot of the uglier parts of the code.

4. I've updated all remaining SOLARIS build flags to the newer XP_SOLARIS, because the SOLARIS flag is no longer set when building Solaris.

5. I've confirmed the workaround in gtxFontconfigFonts.cpp is no longer necessary. The Solaris people got impatient about implementing a half-baked patch for a fontconfig feature that wasn't ready yet back in 2009, and somehow convinced Mozilla to patch their software to work around it when really they should have just fixed or removed their broken fontconfig patch. The feature they wanted has since been implemented properly, and no version of Solaris still uses the broken patch that required this fix. If anyone had ever properly audited this code, it would have been removed a long time ago.
2019-11-04 11:52:13 +08:00
wolfbeast
0a50553673 Issue #187: Remove solaris 1st party code OS checks. 2019-04-04 20:26:29 +08:00
wolfbeast
78d61fd2b1 Issue #187: Remove solaris conditional code. 2019-04-04 20:26:26 +08:00
trav90
cab0faa710 Silence the -Wuninitialized warning in mozjemalloc
GCC 7+ warns about too many false positives.
2019-02-16 00:12:52 +08:00
wolfbeast
1bb41a8652 Revert "Switch to using a single memory allocation arena"
This reverts commit 4ceb21241eacac2911f2fed846359215870f121f.
2019-02-16 00:12:21 +08:00
wolfbeast
91c79f2202 Switch to using a single memory allocation arena 2019-02-16 00:12:05 +08:00
wolfbeast
92fbd042f5 Remove the Dark Matter Detector (DMD) Memeory debugger component.
This resolves #376.
2019-02-15 23:58:31 +08:00
wolfbeast
2531de02eb Remove MOZ_WIDGET_GONK [2/2]
Tag #288
2019-02-15 23:57:10 +08:00
wolfbeast
09f98d848b Remove the unused and rudimentary arena load balancer.
Lock contention is not something we'd easily have to deal with in our application.
This simplifies our code.
2019-02-15 23:52:21 +08:00
wolfbeast
30e71338fd Make our allocator use multiple arenas based on number of CPU cores. 2019-02-15 23:52:20 +08:00
wolfbeast
7ea1703d6b Remove single-threaded considerations.
We assume our applications are always going to have multithreaded access to the malloc.
2019-02-15 23:52:17 +08:00
wolfbeast
46548c6098 Update credits in BSD-licensed files. 2019-02-15 23:52:15 +08:00
wolfbeast
dd3affa0db Remove jemalloc 4 leftover conditional. 2019-02-15 23:52:14 +08:00
wolfbeast
7f3296be1d Remove MOZ_REPLACE_JEMALLOC
This was only defined when building jemalloc4 as a replace-malloc library.
2019-02-15 23:52:12 +08:00
wolfbeast
d804882857 Remove jemalloc 4 from our tree. 2019-02-15 23:52:10 +08:00
wolfbeast
797ca533f9 Remove support for making jemalloc4 the default memory allocator. 2019-02-15 23:52:09 +08:00
wolfbeast
c76d18a40d Remove support for system jemalloc. 2019-02-15 23:52:07 +08:00
Mike Hommey
6837efcaef Bug 1424709 - Force disable the OSX system "nano allocator". r=spohl, a=RyanVM
We're not actually using it, and it messes up with the zone allocator in
mozjemalloc after fork(). See the lengthy analysis in
https://bugzilla.mozilla.org/show_bug.cgi?id=1424709#c34 and following.

--HG--
extra : rebase_source : b191048290a907cc7668ad7ab6369ef8661f31dc
extra : intermediate-source : 45c5d467a46077dcc3ccd59feafd0c2784432fef
extra : source : bf1efa161edb20a83fe8db2f96c51f4e66880153
2019-02-15 23:36:57 +08:00
trav90
cad73db0f2 Use |noexcept| instead of an exception-specification in mozalloc.h
We are using |throw(std::bad_alloc)|, but dynamic exception specifications have been deprecated in C++11. The C++11 equivalent is |noexcept(false)|. This causes build warning spam when using newer compilers such as GCC 7.x.
2019-02-15 23:35:46 +08:00
Roy Tam
dcd9973243 import FIREFOX_52_6_0esr_RELEASE from mozilla-esr52 hg repo 2018-01-19 03:59:58 +08:00