about summary refs log tree commit diff
path: root/configure
Commit message (Collapse)AuthorAgeFilesLines
* configure: enable warnings by defaultRich Felker2020-08-271-2/+2
| | | | | | | now that -Wall is not used and we control which warnings are enabled, it makes sense to have the wanted ones on by default. hopefully this will also discourage manually adding -Wall to CFLAGS and making incorrect changes or bug reports based on the compiler's output.
* configure: use additive warnings instead of subtracting from -WallRich Felker2020-08-271-9/+15
| | | | | | | | | | -Wall varies too much by compiler and version. rather than trying to track all the unwanted style warnings that need to be subtracted, just enable wanted warnings. also, move -Wno-pointer-to-int-cast outside --enable-warnings conditional so that it always applies, since it's turning off a nuisance warning that's on-by-default with most compilers.
* configure: add further -Werror=... options to detected CFLAGSRich Felker2020-08-271-0/+4
| | | | | | | these four warning options were overlooked previously, likely because they're not part of GCC's -Wall. they all detect constraint violations (invalid C at the source level) and should always be on in -Werror form.
* make mallocng the default malloc implementationRich Felker2020-06-301-2/+2
|
* add malloc implementation selection to configureRich Felker2020-06-301-0/+12
| | | | | | the intent here is to keep oldmalloc as an option, at least for the short term, in case any users are negatively impacted in some way by mallocng and need to fallback until their issues are resolved.
* suppress unwanted warnings when configuring with clangRich Felker2020-06-011-0/+7
| | | | | | | | coding style warnings enabled by default in clang have long been a source of spurious questions/bug-reports. since clang provides a -w that behaves differently from gcc's, and that lets us enable any warnings we may actually want after turning them all off to start with a clean slate, use it at configure time if clang is detected.
* ppc: add configure check for older compilers erroring on 'd' constraintrofl0r2019-11-051-0/+9
|
* configure: make AR and RANLIB customizableFangrui Song2019-07-041-0/+4
|
* add riscv64 architecture supportRich Felker2019-06-141-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Author: Alex Suykov <alex.suykov@gmail.com> Author: Aric Belsito <lluixhi@gmail.com> Author: Drew DeVault <sir@cmpwn.com> Author: Michael Clark <mjc@sifive.com> Author: Michael Forney <mforney@mforney.org> Author: Stefan O'Rear <sorear2@gmail.com> This port has involved the work of many people over several years. I have tried to ensure that everyone with substantial contributions has been credited above; if any omissions are found they will be noted later in an update to the authors/contributors list in the COPYRIGHT file. The version committed here comes from the riscv/riscv-musl repo's commit 3fe7e2c75df78eef42dcdc352a55757729f451e2, with minor changes by me for issues found during final review: - a_ll/a_sc atomics are removed (according to the ISA spec, lr/sc are not safe to use in separate inline asm fragments) - a_cas[_p] is fixed to be a memory barrier - the call from the _start assembly into the C part of crt1/ldso is changed to allow for the possibility that the linker does not place them nearby each other. - DTP_OFFSET is defined correctly so that local-dynamic TLS works - reloc.h LDSO_ARCH logic is simplified and made explicit. - unused, non-functional crti/n asm files are removed. - an empty .sdata section is added to crt1 so that the __global_pointer reference is resolvable. - indentation style errors in some asm files are fixed.
* improve i386 inline syscall asm on non-broken compilersRich Felker2019-05-111-0/+14
| | | | | | | | | | | | | | | | | we have to avoid using ebx unconditionally in asm constraints for i386, because gcc 3 and 4 and possibly other simplistic compilers (pcc?) implement PIC via making ebx a fixed-use register, and disallow its use for anything else. rather than hard-coding knowledge of which compilers work (at least gcc 5+ and clang), perform a configure test; this should give us the good codegen on any new compilers we don't yet know about. swapping ebx and edx is kept for 1- and 2-arg syscalls because it avoids having any spills/stack-frame at all in small functions. for 6-arg, if ebx is directly usable, the complex shuffling introduced in commit c8798ef974d21c338a7d8d874a402978ffc6168e can be avoided, and ebp can be loaded the same way ebx is in 5-arg syscalls for compilers that don't support direct use of ebx.
* configure: accept ppc[64] as alias for powerpc[64] in gcc tuplesRich Felker2019-01-191-2/+2
| | | | | apparently some distros use this form, and it seems to be supported in the gcc build system.
* support clang internal assembler when building for arm as thumb2 codeRich Felker2018-09-191-0/+1
| | | | | | the clang internal assembler does not accept assembler options passed via the usual -Wa mechanism, but it does accept -mimplicit-it directly as an option to the compiler driver.
* configure: only try -Qunused-arguments for clangRich Felker2018-09-121-1/+1
| | | | | | | | other compilers don't need this option, but gcc 3 and perhaps others accept it despite not understanding it, then print warnings about it at build time. omitting it when not needed will also help shorten the command lines.
* remove vis.h protected-visibility hackRich Felker2018-09-121-38/+0
| | | | | | | | | since commit dc2f368e565c37728b0d620380b849c3a1ddd78f this has been disabled by default, but was left available in case users unhappy with the resulting size or performance regressions wanted to try to make it work. now that we make widespread use of hidden visibility for internal interfaces, this no longer makes sense. if any costly calls remain they can be fixed with hidden aliases.
* add m68k portRich Felker2018-06-191-0/+8
| | | | | | | | | | | | | three ABIs are supported: the default with 68881 80-bit fpu format and results returned in floating point registers, softfloat-only with the same format, and coldfire fpu with IEEE single/double only. only the first is tested at all, and only under qemu which has fpu emulation bugs. basic functionality smoke tests have been performed for the most common arch-specific breakage via libc-test and qemu user-level emulation. some sysvipc failures remain, but are shared with other big endian archs and will be fixed separately.
* use explicit dynamic-list rather than symbolic-functions for linkingRich Felker2018-04-171-4/+6
| | | | | | | | | | | | | | | | | | | | | we have always bound symbols at libc.so link time rather than runtime to minimize startup-time relocations and overhead of calls through the PLT, and possibly also to preclude interposition that would not work correctly anyway if allowed. historically, binding at link-time was also necessary for the dynamic linker to work, but the dynamic linker bootstrap overhaul in commit f3ddd173806fd5c60b3f034528ca24542aecc5b9 made it unnecessary. our use of -Bsymbolic-functions, rather than -Bsymbolic, was chosen because the latter is incompatible with public global data; it makes it incompatible with copy relocations in the main program. however, not all global data needs to be public. by using --dynamic-list instead with an explicit list, we can reduce the number of symbolic relocations left for runtime. this change will also allow us to permit interposition of specific functions (e.g. the allocator) if/when we want to, by adding them to the dynamic list.
* fix detection of LIBCC for compiler-rt with clangMatúš Olekšák2018-02-211-0/+2
| | | | | | | | | | | Maintainer's note: at one point, -lcompiler_rt apparently worked, and may still work and be preferable if one has manually installed the library in a public lib directory. but with current versions of clang, the full pathname to the library file is needed. the original patch removed the -lcompiler_rt check; I have left it in place in case there are users depending on it, and since, when it does work, it's preferable so as not to code a dependency on the specific compiler version and paths in config.mak.
* better configure check for long double supportSzabolcs Nagy2018-02-071-3/+2
|
* disable global visibility override hack (vis.h) by defaultRich Felker2017-08-111-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | neither current compilers nor linkers treat protected visibility the way I expected, as having fixed source-level semantics rather than being dependent on target-specific ABI details, and change seems unlikely. while the use here does not actually depend on the specific semantics, at least some versions of some linkers, especially lld, refuse to allow linking to a libc.so where the symbols have protected visibility. this cannot be detected at configure-time because linking libc.so itself works fine, and because even if we could test linking an application against libc.so successfully, we could not justifiably assume that the same linker used to link libc.so would also be used later to link applications. disable the vis.h hack by default at the configure level, but add an explicit "auto" option to request the old configure-time detection rather than just removing it. this leaves it easy to evaluate whether it actually resulted in significant size or performance benefits while ensuring that out-of-the-box builds are not unlinkable for some users. fortunately, preliminary evaluation suggests that at least x86_64, arm, and aarch64 don't suffer at all from the change, and impact on other archs is low. if low is not low enough, it should not be hard to analyze where the significant PLT call ABI costs are present and mitigate them without the hack.
* fix clang CFLAGS checks and silence unused argument warningsDmitry Golovin2017-06-231-0/+8
|
* when building for arm as thumb2 code, also request assembly as thumbRich Felker2016-12-191-0/+4
| | | | | | all assembly is now thumb2-compatible. on existing targets this is at best a size optimization, but it will also facilitate porting to thumb2-isa-only arm variants.
* add s390x portBobby Bingham2016-11-111-0/+1
|
* configure: handle mipsisa64* triplet as a mips64 targetSzabolcs Nagy2016-08-301-1/+1
| | | | | the gnu config.sub script recognizes several mipsisa64* cpu types that musl supports as mips64 targets.
* add powerpc64 portBobby Bingham2016-05-081-1/+7
|
* fix redundant processing of --build flag in configure scriptLeMay, Michael2016-05-041-1/+1
| | | | | | | | The --build flag is listed in two case statement entries in configure, which causes the second entry to be ignored. This patch removes it from the first entry. Signed-off-by: Michael LeMay <michael.lemay@intel.com>
* follow standard configure behavior for cross compile prefixRich Felker2016-04-291-1/+13
| | | | | | | | | | | | | | | | the standard configure interface, which our configure script tries to implement, identifies cross compiling (build != host) and searches for the properly-prefixed cross tools. our script was not doing that, forcing users to explicitly provide either CC or a CROSS_COMPILE tool prefix, and the more common choice, just providing CC, was incomplete because the Makefile would still invoke the native ar and ranlib programs. this happened to work when building on ELF-based systems with GNU binutils, but could easily fail when cross-compiling from dissimilar systems. like before, and like the standard configure behavior, an explicit CC or CROSS_COMPILE variable on the command line or in the environment overrides the automatic prefixing.
* add mips n32 port (ILP32 ABI for mips64)Rich Felker2016-04-181-0/+1
| | | | based on patch submitted by Jaydeep Patil, with minor changes.
* add support for mips and mips64 r6 isaRich Felker2016-04-031-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | mips32r6 and mips64r6 are actually new isas at both the asm source and opcode levels (pre-r6 code cannot run on r6) and thus need to be treated as a new subarch. the following changes are made, some of which yield code generation improvements for non-r6 targets too: - add subarch logic in configure script and reloc.h files for dynamic linker name. - suppress use of .set mips2 asm directives (used to allow mips2 atomic instructions on baseline mips1 builds; the kernel has to emulate them on mips1) except when actually needed. they cause wrong instruction encodings on r6, and pessimize inlining on at least some compilers. - only hard-code sync instruction encoding on mips1. - use "ZC" constraint instead of "m" constraint for llsc memory operands on r6, where the ll/sc instructions no longer accept full 16-bit offsets. - only hard-code rdhwr instruction encoding with .word on targets (pre-r2) where it may need trap-and-emulate by the kernel. otherwise, just use the instruction mnemonic, and allow an arbitrary destination register to be used.
* make configure check for unsupported (SPE) powerpc hard-float modelsRich Felker2016-03-061-0/+2
| | | | | | the SPE ABI may be compatible with soft-float, but actually making it work requires some additional work, so for now it's best to make sure broken builds don't happen.
* add powerpc soft-float supportFelix Fietkau2016-03-061-0/+4
| | | | | | | | | Some PowerPC CPUs (e.g. Freescale MPC85xx) have a completely different instruction set for floating point operations (SPE). Executing regular PowerPC floating point instructions results in "Illegal instruction" errors. Make it possible to run these devices in soft-float mode.
* add mips64 portRich Felker2016-03-061-1/+7
| | | | | patch by Mahesh Bodapati and Jaydeep Patil of Imagination Technologies.
* add arch tuple matching for nt32 and nt64 in configureRich Felker2016-02-191-0/+2
| | | | | | | | | the nt32 and nt64 archs will be provided by the midipix project for building musl on top of its posix-like syscall layer for windows. at present the needed arch files are in a separate repository, but having the tuple matching in the upstream configure script should make it possible to overlay the arch files without needing any further patching.
* work around regression building for armhf with clang (compiler bug)Rich Felker2016-02-191-0/+14
| | | | | | | | | commit e4355bd6bec89688e8c739cd7b4c76e675643dca moved the math asm from external source files to inline asm, but unfortunately, all current releases of clang use the wrong inline asm constraint codes for float and double ("w" and "P" instead of "t" and "w", respectively). this patch adds detection for the bug in configure, and, for now, just disables the affected asm on broken clang versions.
* partly revert detection of broken float in configureRich Felker2016-02-181-1/+1
| | | | | | | | | commit 80fbaac4cd1930e9545a5d36bf46ae49011d2ce8 broke all soft-float archs, where gcc defines __GCC_IEC_559==0 because rounding modes and exception flags are not supported. for now, just check for __FAST_MATH__ as an indication of broken float. this won't detect all possible misconfigurations but it probably catches the most common one.
* make configure attempt to catch broken floating point CFLAGS/defaultsRich Felker2016-02-171-0/+10
|
* make configure accept -h as an alias for --helpRich Felker2016-02-021-1/+1
|
* don't suppress shared libc when linker lacks -Bsymbolic-functionsRich Felker2016-01-311-9/+4
| | | | | | | | | | | previous work overhauling the dynamic linker made it so that linking libc with -Bsymbolic-functions was no longer mandatory, but the configure logic that forced --disable-shared when ld failed to accept the option was left in place. this commit removes the hard-coded -Bsymbolic-functions from the Makefile and changes the configure test to one that simply adds it to the auto-detected LDFLAGS on success.
* add arch/generic include fallback to build rulesRich Felker2016-01-271-2/+3
| | | | | | this sets the stage for the first phase of the bits deduplication. bits headers which are identical for "most" archs will be moved to arch/generic/bits.
* remove unneeded -I options from configure test for may_alias attributeRich Felker2016-01-271-1/+1
| | | | | this test does not include anything, so the -I options are not useful and are just a maintenance burden if paths change.
* use same object files for libc.a and libc.so if compiler produces PICRich Felker2016-01-251-0/+10
| | | | | | | | | | | | | | | | now that .lo and .o files differ only by whether -fPIC is passed (and no longer at the source level based on the SHARED macro), it's possible to use the same object files for both static and shared libc when the compiler would produce PIC for the static files anyway. this happens if the user has included -fPIC in their CFLAGS or if the compiler has been configured to produce PIE by default. we use the .lo files for both, and still append -fPIC to the CFLAGS, rather than using the .o files so that libc.so does not break catastrophically if the user later removes -fPIC from CFLAGS in config.mak or on the make command line. this also ensures that we get full -fPIC in case -fpic, -fPIE, or some other lesser-PIC option was passed in CFLAGS.
* fix global visibility (vis.h) support for out-of-tree buildsRich Felker2016-01-201-1/+1
| | | | | | commit 2f853dd6b9a95d5b13ee8f9df762125e0588df5d failed to change the test for -include vis.h support to use $srcdir, so vis.h was always disabled by configure for out-of-tree builds.
* support out-of-tree buildPetr Hosek2016-01-171-5/+25
| | | | | | | | | | | | this change adds support for building musl outside of the source tree. the implementation is similar to autotools where running configure in a different directory creates config.mak in the current working directory and symlinks the makefile, which contains the logic for creating all necessary directories and resolving paths relative to the source directory. to support both in-tree and out-of-tree builds with implicit make rules, all object files are now placed into a separate directory.
* work around toolchains with broken visibility in libgcc/libpccRich Felker2015-11-071-0/+5
|
* have configure check/add --gc-sections linker optionRich Felker2015-11-041-0/+4
| | | | | | | | this allowing the linker to drop certain weak definitions that are only used as dummies for static linking. they could be eliminated for shared library builds using the preprocessor instead, but we are trying to transition to using the same object files for shared and static libc, so a link-time solution is preferable.
* have configure check/add linker options to reduce size lost to paddingRich Felker2015-11-041-0/+6
| | | | | | based on patch by Denys Vlasenko. sorting sections and common data symbols by alignment acts as an approximation for optimal packing, which the linker does not actually support.
* have configure check/add -ffunction-sections and -fdata-sectionsRich Felker2015-11-041-0/+11
| | | | | | | | | | | | | | | | | | based on patch by Denys Vlasenko. the original intent for using these options was to enable linking optimizations. these are immediately available for static linking applications to libc.a, and will also be used for linking libc.so in a subsequent commit. in addition to the original motives, this change works around a whole class of toolchain bugs where the compiler generates relative address expressions using a weak symbol and the assembler "optimizes out" the relocation which should result by using the weak definition. (see gas pr 18561 and gcc pr 66609, 68178, etc. for examples.) by having different functions and data objects in their own sections, all relative address expressions are cross-section and thus cannot be resolved to constants until link time. this allows us to retain support for affected compiler/assembler versions without invasive and fragile source-level workarounds.
* keep user-provided CFLAGS/LDFLAGS separate from those added by configureRich Felker2015-11-021-2/+4
| | | | | | this way, overriding these variables on the make command line (or just re-passing the originally-passed values when invoking make) won't suppress use of the flags added by configure.
* prevent user CFLAGS overrides from exposing executable stackRich Felker2015-10-231-7/+7
| | | | | | | | | | | the option to suppress executable stack tagging was placed in CFLAGS, which is treated as optional and overridable by the build system. if a user replaces CFLAGS after configure has run, it could get lost, resulting in a libc.so that's flagged as needing executable stack, which would cause the kernel to map the initial stack as executable. move -Wa,--noexecstack to CFLAGS_C99FSE, the make variable used for mandatory compiler options.
* suppress sh assembler rejection of instructions based on isa levelRich Felker2015-10-151-0/+1
| | | | | | we need access to all instructions in order for runtime selection of atomic model to work correctly. without this patch, some versions of gcc instruct gas to reject instructions outside the target isa level.
* eliminate protected-visibility data in libc.so with vis.h preincludeRich Felker2015-09-291-3/+11
| | | | | | | | | | | | | | | some newer binutils versions print scary warnings about protected data because most gcc versions fail to produce the right address references/relocations for such data that might be subject to copy relocations. originally vis.h explicitly assigned default visibility to all public data symbols to avoid this issue, but commit b8dda24fe1caa901a99580f7a52defb95aedb67c removed this treatment for stdin/out/err to work around a gcc 3.x bug, and since they don't actually need it (because taking their addresses is not valid C). instead, a check for the gcc 3.x bug is added to the configure check for vis.h preinclude support; this feature will simply be disabled when using a buggy version of gcc.
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-11-12 06:59:13 +0000