- 06 12月, 2012 4 次提交
-
-
由 Rich Felker 提交于
the issue is identical to the recent commit fixing the mips versions: despite other implementations doing this, it conflicts with the requirements of ISO C and it's a waste of time and code size.
-
由 Rich Felker 提交于
previously, everything was going through an intermediate conversion to long double, which caused the extern __fpclassifyl function to get invoked, preventing virtually all optimizations of these operations. with the new code, tests on constant float or double arguments compile to a constant 0 or 1, and tests on non-constant expressions are efficient. I may later add support for __builtin versions on compilers that support them.
-
由 Rich Felker 提交于
nothing in the standard requires or even allows the fenv state to be restored by longjmp. restoring the exception flags is not such a big deal since it's probably valid to clobber them completely, but restoring the rounding mode yields an observable side effect not sanctioned by ISO C. saving/restoring it also wastes a few cycles and 16 bytes of code. as for historical behavior, reportedly SGI IRIX did save/restore fenv, and this is where glibc and uClibc got the behavior from. a few other systems save/restore it too (on archs other than mips), even though this is apparently wrong. further details are documented here: http://www-personal.umich.edu/~williams/archive/computation/setjmp-fpmode.html as musl aims for standards conformance rather than coddling historical programs expecting non-conforming behavior, and as it's unlikely that any historical programs actually depend on the incorrect behavior (such programs would break on other archs, anyway), I'm making the change not to save/restore fenv on mips.
-
由 Rich Felker 提交于
due to some historical oddity, these are considered libc headers rather than kernel headers. the kernel used to provide them too, but it seems modern kernels do not install them, so let's just do the easiest thing and provide them. stripped-down versions provided by John Spencer.
-
- 05 12月, 2012 2 次提交
-
-
由 Rich Felker 提交于
apparently recent gcc versions have intentionally broken the traditional definition by treating it as a non-constant expression. the traditional definition may also be problematic for c++ programs.
-
由 Rich Felker 提交于
for some reason I have not been able to determine, gcc 3.2 rejects the array notation. this seems to be a gcc bug, but since it's easy to work around, let's do the workaround and avoid gratuitously requiring newer compilers.
-
- 04 12月, 2012 3 次提交
-
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
reportedly this is a semi-common practice among some BSDs and a few other systems, and will improve application compatibility.
-
由 Rich Felker 提交于
previously, a few BSD features were enabled only by _BSD_SOURCE, not by _GNU_SOURCE. since _BSD_SOURCE is default in the absence of other feature test macros, this made adding _GNU_SOURCE to a project not a purely additive feature test macro; it actually caused some features to be suppressed. most of the changes made by this patch actually bring musl in closer alignment with the glibc behavior for _GNU_SOURCE. the only exceptions are the added visibility of functions like strlcpy which were BSD-only due to being disliked/rejected by glibc maintainers. here, I feel the consistency of having _GNU_SOURCE mean "everything", and especially the property of it being purely additive, are more valuable than hiding functions which glibc does not have.
-
- 03 12月, 2012 1 次提交
-
-
由 Rich Felker 提交于
most importantly, the format/scan macros for the [u]int_fast16_t and [u]int_fast32_t types were defined incorrectly assuming these types would match the native word/pointer size. this is incorrect on any 64-bit system; the "fast" types for 16- and 32-bit integers are simply int. another issue which was "only a warning" (despite being UB) is that the choice of "l" versus "ll" was incorrect for 64-bit types on 64-bit machines. while it would "work" to always use "long long" for 64-bit types, we use "long" on 64-bit machines to match what glibc does and what the ABI documents recommend. the macro definitions were probably right in very old versions of musl, but became wrong when we aligned most closely with the 'standard' ABI. checking UINTPTR_MAX is an easy way to get the system wordsize without pulling in new headers. finally, the useless __PRIPTR macro to allow the underlying type of [u]intptr_t to vary has been removed. we are using "long" on all targets, and thankfully this matches what glibc does, so I do not envision ever needing to change it. thus, the "l" has just been incorporated directly in the strings.
-
- 01 12月, 2012 2 次提交
-
-
由 Rich Felker 提交于
this fixes a regression related to the changes made to bits/signal.h between 0.9.7 and 0.9.8 that broke some (non-portable) software.
-
由 Rich Felker 提交于
previously, shared library constructors were being called before important internal things like the environment (extern char **environ) and hwcap flags (needed for sjlj to work right with float on arm) were initialized in __libc_start_main. rather than trying to have to dynamic linker make sure this stuff all gets initialized right, I've opted to just defer calling shared library constructors until after the main program's entry point is reached. this also fixes the order of ctors to be the exact reverse of dtors, which is a desirable property and possibly even mandated by some languages. the main practical effect of this change is that shared libraries calling getenv from ctors will no longer fail.
-
- 27 11月, 2012 5 次提交
-
-
由 Rich Felker 提交于
these should have little/no practical impact but they're needed for strict conformance.
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
if these are to be supported, they belong in the main stat.h, not repeated for each arch.
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
the missing check did not affect the default profile, since it has both _XOPEN_SOURCE and _BSD_SOURCE defined, but it did break programs which explicitly define _BSD_SOURCE, causing it to be the only feature test macro present.
-
- 26 11月, 2012 4 次提交
-
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
these structures are purely for use by trace/debug tools and tools working with core files. the definition of fpregset_t, which was previously here, has been removed because it was wrong; fpregset_t should be the type used in mcontext_t, not the type used in ptrace/core stuff.
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
actually, the hard-coded name should be eliminated too, and replaced by a search for the soname in the headers, but that can be done separately later.
-
- 24 11月, 2012 9 次提交
-
-
由 Rich Felker 提交于
aside from microblaze, these should be roughly correct for all archs now. some misc junk macros and typedefs are missing, which should probably be added for max compatibility with trace/debug tools.
-
由 Rich Felker 提交于
it should now really match the kernel. some of the removed padding corresponded to the difference between user and kernel sigset_t. the space at the end was redundant with the uc_mcontext member and seems to have been added as a result of misunderstanding glibc's definition versus the kernel's.
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
with these changes, the members/types of mcontext_t and related stuff should closely match the glibc definitions. unlike glibc, however, the definitions here avoid using typedefs as much as possible and work directly with the underlying types, to minimize namespace pollution from signal.h in the default (_BSD_SOURCE) profile. this is a first step in improving compatibility with applications which poke at context/register information -- mainly debuggers, trace utilities, etc. additional definitions in ucontext.h and other headers may be needed later. if feature test macros are used to request a conforming namespace, mcontext_t is replaced with an opaque structure of the equivalent size and alignment; conforming programs cannot examine its contents anyway.
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
these fields were wrongly copied from the kernel's ppc64 struct def
-
- 22 11月, 2012 6 次提交
-
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
unlike the previous definition, NSIG/_NSIG is supposed to be one more than the highest signal number. adding this will allow simplifying libc-internal code that makes signal-related syscalls, which can be done as a later step. some apps might use it too; while this usage is questionable, it's at least not insane.
-
由 Rich Felker 提交于
also handle the non-GNUC case where alignment attribute is not available by simply omitting it. this will not cause problems except for inclusion of mcontex_t/ucontext_t in application-defined structures, since the natural alignment of the uc_mcontext member relative to the start of ucontext_t is already correct. and shame on whoever designed this for making it impossible to satisfy the ABI requirements without GNUC extensions.
-
由 Rich Felker 提交于
-
- 21 11月, 2012 1 次提交
-
-
由 rofl0r 提交于
-
- 19 11月, 2012 3 次提交
-
-
由 rofl0r 提交于
sigsetjmp: store temporaries in jmp_buf rather than on stack.
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
it's essential to decrement the stack pointer before writing to new stack space, rather than afterwards. otherwise there is a race condition during which asynchronous code (signals) could clobber the data being stored. it may be possible to optimize the code further using stwu, but I wanted to avoid making any changes to the actual stack layout in this commit. further improvements can be made separately if desired.
-