summaryrefslogtreecommitdiffstats
path: root/configure.ac
Commit message (Collapse)AuthorAgeFilesLines
...
* Don't rely on OSX SDK malloc/malloc.h for malloc_zone struct definitionsMike Hommey2017-01-181-31/+0
| | | | | | | | | | The SDK jemalloc is built against might be not be the latest for various reasons, but the resulting binary ought to work on newer versions of OSX. In order to ensure this, we need the fullest definitions possible, so copy what we need from the latest version of malloc/malloc.h available on opensource.apple.com.
* Add huge page configuration and pages_[no}huge().Jason Evans2016-12-271-3/+41
| | | | | | | | Add the --with-lg-hugepage configure option, but automatically configure LG_HUGEPAGE even if it isn't specified. Add the pages_[no]huge() functions, which toggle huge page state via madvise(..., MADV_[NO]HUGEPAGE) calls.
* Restructure *CFLAGS/*CXXFLAGS configuration.Jason Evans2016-12-161-122/+152
| | | | | | | | | | | | | Convert CFLAGS/CXXFLAGS to be concatenations: CFLAGS := CONFIGURE_CFLAGS SPECIFIED_CFLAGS EXTRA_CFLAGS CXXFLAGS := CONFIGURE_CXXFLAGS SPECIFIED_CXXFLAGS EXTRA_CXXFLAGS This ordering makes it possible to override the flags set by the configure script both during and after configuration, with CFLAGS/CXXFLAGS and EXTRA_CFLAGS/EXTRA_CXXFLAGS, respectively. This resolves #504.
* jemalloc cpp new/delete bindingsDave Watson2016-12-131-0/+72
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Adds cpp bindings for jemalloc, along with necessary autoconf settings. This is mostly to add sized deallocation support, which can't be added from C directly. Sized deallocation is ~10% microbench improvement. * Import ax_cxx_compile_stdcxx.m4 from the autoconf repo, seems like the easiest way to get c++14 detection. * Adds various other changes, like CXXFLAGS, to configure.ac. * Adds new rules to Makefile.in for src/jemalloc-cpp.cpp, and a basic unittest. * Both new and delete are overridden, to ensure jemalloc is used for both. * TODO future enhancement of avoiding extra PLT thunks for new and delete - sdallocx and malloc are publicly exported jemalloc symbols, using an alias would link them directly. Unfortunately, was having trouble getting it to play nice with jemalloc's namespace support. Testing: Tested gcc 4.8, gcc 5, gcc 5.2, clang 4.0. Only gcc >= 5 has sized deallocation support, verified that the rest build correctly. Tested mac osx and Centos. Tested --with-jemalloc-prefix and --without-export. This resolves #202.
* Add --disable-syscall.Jason Evans2016-12-041-9/+22
| | | | This resolves #517.
* Implement a more reliable detection scheme for os_unfair_lock.John Szakmeister2016-11-231-0/+5
| | | | | | | | | | | | The core issue here is the weak linking of the symbol, and in certain environments--for instance, using the latest Xcode (8.1) with the latest SDK (10.12)--os_unfair_lock may resolve even though you're compiling on a host that doesn't support it (10.11). We can use the availability macros to circumvent this problem, and detect that we're not compiling for a target that is going to support them and error out at compile time. The other alternative is to do a runtime check, but that presents issues for cross-compiling.
* Add pthread_atfork(3) feature test.Jason Evans2016-11-171-0/+8
| | | | | | Some versions of Android provide a pthreads library without providing pthread_atfork(), so in practice a separate feature test is necessary for the latter.
* Refactor madvise(2) configuration.Jason Evans2016-11-171-13/+25
| | | | | | | | | Add feature tests for the MADV_FREE and MADV_DONTNEED flags to madvise(2), so that MADV_FREE is detected and used for Linux kernel versions 4.5 and newer. Refactor pages_purge() so that on systems which support both flags, MADV_FREE is preferred over MADV_DONTNEED. This resolves #387.
* Remove a residual comment.Jason Evans2016-11-171-1/+0
|
* Revert "Add JE_RUNNABLE() and use it for os_unfair_lock_*() test."Jason Evans2016-11-161-16/+1
| | | | | | This reverts commit a2e601a2236315fb6f994ff364ea442ed0aed07b. JE_RUNNABLE() causes general cross-compilation issues.
* Add JE_RUNNABLE() and use it for os_unfair_lock_*() test.Jason Evans2016-11-121-1/+16
| | | | This resolves #494.
* Add configure support for *-*-linux-android.Jason Evans2016-11-101-0/+12
| | | | | | | This is tailored to Android, i.e. more specific than the *-*-linux* configuration. This resolves #471.
* Use -std=gnu11 if available.Jason Evans2016-11-041-2/+8
| | | | This supersedes -std=gnu99, and enables C11 atomics.
* Support Debian GNU/kFreeBSD.Samuel Moritz2016-11-031-1/+1
| | | | Treat it exactly like Linux since they both use GNU libc.
* Fix sycall(2) configure test for Linux.Jason Evans2016-11-031-2/+1
|
* Do not use syscall(2) on OS X 10.12 (deprecated).Jason Evans2016-11-031-0/+17
|
* Add os_unfair_lock support.Jason Evans2016-11-031-0/+14
| | | | | OS X 10.12 deprecated OSSpinLock; os_unfair_lock is the recommended replacement.
* Force no lazy-lock on Windows.Jason Evans2016-11-021-5/+11
| | | | | | | Monitoring thread creation is unimplemented for Windows, which means lazy-lock cannot function correctly. This resolves #310.
* Use CLOCK_MONOTONIC_COARSE rather than COARSE_MONOTONIC_RAW.Jason Evans2016-10-301-6/+6
| | | | | | | | The raw clock variant is slow (even relative to plain CLOCK_MONOTONIC), whereas the coarse clock variant is faster than CLOCK_MONOTONIC, but still has resolution (~1ms) that is adequate for our purposes. This resolves #479.
* Fix EXTRA_CFLAGS to not affect configuration.Jason Evans2016-10-301-4/+2
|
* Only link with libm (-lm) if necessary.Jason Evans2016-10-281-3/+12
| | | | This fixes warnings when building with MSVC.
* Only use --whole-archive with gcc.Jason Evans2016-10-281-0/+3
| | | | | | | Conditionalize use of --whole-archive on the platform plus compiler, rather than on the ABI. This fixes a regression caused by 7b24c6e5570062495243f1e55131b395adb31e33 (Use --whole-archive when linking integration tests on MinGW.).
* Do not force lazy lock on Windows.Jason Evans2016-10-271-1/+0
| | | | | | | | This reverts 13473c7c66a81a4dc1cf11a97e9c8b1dbb785b64, which was intended to work around bootstrapping issues when linking statically. However, this actually causes problems in various other configurations, so this reversion may force a future fix for the underlying problem, if it still exists.
* Refine nstime_update().Jason Evans2016-10-101-8/+41
| | | | | | | | | | | | | | | | | | | | | Add missing #include <time.h>. The critical time facilities appear to have been transitively included via unistd.h and sys/time.h, but in principle this omission was capable of having caused clock_gettime(CLOCK_MONOTONIC, ...) to have been overlooked in favor of gettimeofday(), which in turn could cause spurious non-monotonic time updates. Refactor nstime_get() out of nstime_update() and add configure tests for all variants. Add CLOCK_MONOTONIC_RAW support (Linux-specific) and mach_absolute_time() support (OS X-specific). Do not fall back to clock_gettime(CLOCK_REALTIME, ...). This was a fragile Linux-specific workaround, which we're unlikely to use at all now that clock_gettime(CLOCK_MONOTONIC_RAW, ...) is supported, and if we have no choice besides non-monotonic clocks, gettimeofday() is only incrementally worse.
* Fix a bug in __builtin_unreachable configure checkElliot Ronaghan2016-09-261-1/+1
| | | | | | | In 1167e9e, I accidentally tested je_cv_gcc_builtin_ffsl instead of je_cv_gcc_builtin_unreachable (copy-paste error), which meant that JEMALLOC_INTERNAL_UNREACHABLE was always getting defined as abort even if __builtin_unreachable support was detected.
* Disable irrelevant Cray compiler warnings if cc-silence is enabledElliot Ronaghan2016-07-071-0/+6
| | | | | | | | | | | | | | Cray is pretty warning-happy, so disable ones that aren't helpful. Each warning has a numeric value instead of having named flags to disable specific warnings. Disable warnings 128 and 1357. 128: Ignore unreachable code warning. Cray warns about `not_reached()` not being reachable in a couple of places because it detects that some loops will never terminate. 1357: Ignore warning about redefinition of malloc and friends With this patch, Cray 8.4.0 and 8.5.1 build cleanly and pass `make check`
* Add Cray compiler's equivalent of -Werror before __attribute__ checksElliot Ronaghan2016-07-071-0/+4
| | | | | | Cray uses -herror_on_warning instead of -Werror. Use it everywhere -Werror is currently used for __attribute__ checks so configure actually detects they're not supported.
* Disable automatic dependency generation for the Cray compilerElliot Ronaghan2016-07-071-0/+4
| | | | | | | | Cray only supports `-M` for generating dependency files. It does not support `-MM` or `-MT`, so don't try to use them. I just reused the existing mechanism for turning auto-dependency generation off (`CC_MM=`), but it might be more principled to add a configure test to check if the compiler supports `-MM` and `-MT`, instead of manually tracking which compilers don't support those flags.
* Add initial support for building with the cray compilerElliot Ronaghan2016-07-071-0/+32
| | | | | | | | | | | | | | | | | Get jemalloc building and passing `make check_unit` with cray 8.4. An inlining bug in 8.4 results in internal errors while trying to build jemalloc. This has already been reported and fixed for the 8.5 release. In order to work around the inlining bug, disable gnu compatibility and limit ipa optimizations. I copied the msvc compiler check for cray, but note that we perform the test even if we think we're using gcc because cray pretends to be gcc if `-hgnu` (which is enabled by default) is used. I couldn't come up with a principled way to check for the inlining bug, so instead I just checked compiler versions. The build had lots of warnings I need to address and cray doesn't support -MM or -MT for dependency tracking, so I had to do `make CC_MM=`.
* Check for __builtin_unreachable at configure timeElliot Ronaghan2016-07-071-0/+17
| | | | | | | | | | | | | | | | | | | Add a configure check for __builtin_unreachable instead of basing its availability on the __GNUC__ version. On OS X using gcc (a real gcc, not the bundled version that's just a gcc front-end) leads to a linker assertion: https://github.com/jemalloc/jemalloc/issues/266 It turns out that this is caused by a gcc bug resulting from the use of __builtin_unreachable(): https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57438 To work around this bug, check that __builtin_unreachable() actually works at configure time, and if it doesn't use abort() instead. The check is based on https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57438#c21. With this `make check` passes with a homebrew installed gcc-5 and gcc-6.
* Fix librt detection when using a Cray compiler wrapperElliot Ronaghan2016-07-071-0/+14
| | | | | | | | | | | | | | | | | | | | | The Cray compiler wrappers will often add `-lrt` to the base compiler with `-static` linking (the default at most sites.) However, `-lrt` isn't automatically added with `-dynamic`. This means that if jemalloc was built with `-static`, but then used in a program with `-dynamic` jemalloc won't have detected that librt is a dependency. The integration and stress tests use -dynamic, which is causing undefined references to clock_gettime(). This just adds an extra check for librt (ignoring the autoconf cache) with `-dynamic` thrown. It also stops filtering librt from the integration tests. With this `make check` passes for: - PrgEnv-gnu - PrgEnv-intel - PrgEnv-pgi PrgEnv-cray still needs more work (will be in a separate patch.)
* Add -dynamic for integration and stress tests with Cray compiler wrappersElliot Ronaghan2016-07-071-0/+18
| | | | | | | | | | | | | | | | | | | Cray systems come with compiler wrappers to simplify building parallel applications. CC is the C++ wrapper, and cc is the C wrapper. The wrappers call the base {Cray, Intel, PGI, or GNU} compiler with vendor specific flags. The "Programming Environment" (prgenv) that's currently loaded determines the base compiler. e.g. compiling with gnu looks something like: module load PrgEnv-gnu cc hello.c On most systems the wrappers defaults to `-static` mode, which causes them to only look for static libraries, and not for any dynamic ones (even if the dynamic version was explicitly listed.) The integration and stress tests expect to be using the .so, so we have to run the with -dynamic so that wrapper will find/use the .so.
* Remove redzone support.Jason Evans2016-05-131-2/+1
| | | | This resolves #369.
* Remove quarantine support.Jason Evans2016-05-131-1/+1
|
* Remove Valgrind support.Jason Evans2016-05-131-30/+0
|
* Modify pages_map() to support mapping uncommitted virtual memory.Jason Evans2016-05-061-0/+2
| | | | | | | | | | | If the OS overcommits: - Commit all mappings in pages_map() regardless of whether the caller requested committed memory. - Linux-specific: Specify MAP_NORESERVE to avoid unfortunate interactions with heuristic overcommit mode during fork(2). This resolves #193.
* Link against librt for clock_gettime(2) if glibc < 2.17.Jason Evans2016-05-041-8/+2
| | | | | | | Link libjemalloc against librt if clock_gettime(2) is in librt rather than libc, as for versions of glibc prior to 2.17. This resolves #349.
* Enable -Wsign-compare warnings.Chris Peterson2016-03-151-0/+1
|
* Add --with-version.Jason Evans2016-03-151-20/+29
| | | | | | Also avoid deleting the VERSION file while trying to (re)generate it. This resolves #305.
* Compile with -Wshorten-64-to-32.Jason Evans2016-02-241-0/+1
| | | | | This will prevent accidental creation of potential integer truncation bugs when developing on LP64 systems.
* Fix overflow in prng_range().Jason Evans2016-02-211-1/+13
| | | | | Add jemalloc_ffs64() and use it instead of jemalloc_ffsl() in prng_range(), since long is not guaranteed to be a 64-bit type.
* Add CPU "pause" intrinsic for MSVCrustyx2016-02-201-6/+16
|
* Fix error "+ 2")syntax error: invalid arithmetic operator (error token is " ↵rustyx2016-02-201-1/+1
| | | | in Cygwin x64
* Detect LG_SIZEOF_PTR depending on MSVC platform targetrustyx2016-02-201-6/+11
|
* Add --with-malloc-conf.Jason Evans2016-02-201-0/+10
| | | | | Add --with-malloc-conf, which makes it possible to embed a default options string during configuration.
* Use AC_CONFIG_AUX_DIR([build-aux]).Jason Evans2015-11-121-0/+2
| | | | This resolves #293.
* Link test to librt if it contains clock_gettime(2).Jason Evans2015-09-151-0/+9
| | | | This resolves #257.
* Address portability issues on Solaris.Jason Evans2015-09-151-1/+2
| | | | | | | | Don't assume Bourne shell is in /bin/sh when running size_classes.sh . Consider __sparcv9 a synonym for __sparc64__ when defining LG_QUANTUM. This resolves #275.
* Fix TLS configuration.Jason Evans2015-09-021-8/+14
| | | | | | | | Fix TLS configuration such that it is enabled by default for platforms on which it works correctly. This regression was introduced by ac5db02034c01357a4ce90504886046a58117921 (Make --enable-tls and --enable-lazy-lock take precedence over configure.ac-hardcoded defaults).
* Stop forcing --enable-munmap on MinGW.Jason Evans2015-08-121-4/+0
| | | | | This is no longer necessary because of the more general chunk merge/split approach to dealing with map coalescing.
generated by cgit v0.12 at 2025-04-05 13:31:40 (GMT)