| Commit message (Expand) | Author | Age | Files | Lines |
|---|
| * | add explicit barrier operation to internal atomic.h API | Rich Felker | 2014-10-10 | 1 | -1/+3 |
| * | add new syscall numbers for seccomp, getrandom, memfd_create•••these syscalls are new in linux v3.17 and present on all supported
archs except sh.
seccomp was added in commit 48dc92b9fc3926844257316e75ba11eb5c742b2c
it has operation, flags and pointer arguments (if flags==0 then it is
the same as prctl(PR_SET_SECCOMP,...)), the uapi header for flag
definitions is linux/seccomp.h
getrandom was added in commit c6e9d6f38894798696f23c8084ca7edbf16ee895
it provides an entropy source when open("/dev/urandom",..) would fail,
the uapi header for flags is linux/random.h
memfd_create was added in commit 9183df25fe7b194563db3fec6dc3202a5855839c
it allows anon mmap to have an fd, that can be shared, sealed and needs no
mount point, the uapi header for flags is linux/memfd.h
| Szabolcs Nagy | 2014-10-08 | 1 | -0/+6 |
| * | add threads.h and needed per-arch types for mtx_t and cnd_t•••based on patch by Jens Gustedt.
mtx_t and cnd_t are defined in such a way that they are formally
"compatible types" with pthread_mutex_t and pthread_cond_t,
respectively, when accessed from a different translation unit. this
makes it possible to implement the C11 functions using the pthread
functions (which will dereference them with the pthread types) without
having to use the same types, which would necessitate either namespace
violations (exposing pthread type names in threads.h) or incompatible
changes to the C++ name mangling ABI for the pthread types.
for the rest of the types, things are much simpler; using identical
types is possible without any namespace considerations.
| Rich Felker | 2014-09-06 | 1 | -0/+2 |
| * | fix build error on arm due to new a_spin code•••this was broken by commit ea818ea8340c13742a4f41e6077f732291aea4bc.
| Rich Felker | 2014-08-25 | 1 | -1/+1 |
| * | add working a_spin() atomic for non-x86 targets•••conceptually, a_spin needs to be at least a compiler barrier, so the
compiler will not optimize out loops (and the load on each iteration)
while spinning. it should also be a memory barrier, or the spinning
thread might keep spinning without noticing stores from other threads,
thus delaying for longer than it should.
ideally, an optimal a_spin implementation that avoids unnecessary
cache/memory contention should be chosen for each arch, but for now,
the easiest thing is to perform a useless a_cas on the calling
thread's stack.
| Rich Felker | 2014-08-25 | 1 | -0/+1 |
| * | add max_align_t definition for C11 and C++11•••unfortunately this needs to be able to vary by arch, because of a huge
mess GCC made: the GCC definition, which became the ABI, depends on
quirks in GCC's definition of __alignof__, which does not match the
formal alignment of the type.
GCC's __alignof__ unexpectedly exposes the an implementation detail,
its "preferred alignment" for the type, rather than the formal/ABI
alignment of the type, which it only actually uses in structures. on
most archs the two values are the same, but on some (at least i386)
the preferred alignment is greater than the ABI alignment.
I considered using _Alignas(8) unconditionally, but on at least one
arch (or1k), the alignment of max_align_t with GCC's definition is
only 4 (even the "preferred alignment" for these types is only 4).
| Rich Felker | 2014-08-20 | 1 | -0/+2 |
| * | make pointers used in robust list volatile•••when manipulating the robust list, the order of stores matters,
because the code may be asynchronously interrupted by a fatal signal
and the kernel will then access the robust list in what is essentially
an async-signal context.
previously, aliasing considerations made it seem unlikely that a
compiler could reorder the stores, but proving that they could not be
reordered incorrectly would have been extremely difficult. instead
I've opted to make all the pointers used as part of the robust list,
including those in the robust list head and in the individual mutexes,
volatile.
in addition, the format of the robust list has been changed to point
back to the head at the end, rather than ending with a null pointer.
this is to match the documented kernel robust list ABI. the null
pointer, which was previously used, only worked because faults during
access terminate the robust list processing.
| Rich Felker | 2014-08-17 | 1 | -1/+1 |
| * | clean up unused and inconsistent atomics in arch dirs•••the a_cas_l, a_swap_l, a_swap_p, and a_store_l operations were
probably used a long time ago when only i386 and x86_64 were
supported. as other archs were added, support for them was
inconsistent, and they are obviously not in use at present. having
them around potentially confuses readers working on new ports, and the
type-punning hacks and inconsistent use of types in their definitions
is not a style I wish to perpetuate in the source tree, so removing
them seems appropriate.
| Rich Felker | 2014-07-27 | 1 | -5/+0 |
| * | add syscall numbers for the new renameat2 syscall•••it's like rename but with flags eg. to allow atomic exchange of two files,
introduced in linux 3.15 commit 520c8b16505236fc82daa352e6c5e73cd9870cff
| Szabolcs Nagy | 2014-07-20 | 1 | -0/+2 |
| * | refactor to remove arch-specific relocation code from dynamic linker•••this was one of the main instances of ugly code duplication: all archs
use basically the same types of relocations, but roughly equivalent
logic was duplicated for each arch to account for the different naming
and numbering of relocation types and variation in whether REL or RELA
records are used.
as an added bonus, both REL and RELA are now supported on all archs,
regardless of which is used by the standard toolchain.
| Rich Felker | 2014-06-18 | 1 | -25/+12 |
| * | dynamic linker: permit error returns from arch-specific reloc function•••the immediate motivation is supporting TLSDESC relocations which
require allocation and thus may fail (unless we pre-allocate), but
this mechanism should also be used for throwing an error on
unsupported or invalid relocation types, and perhaps in certain cases,
for reporting when a relocation is not satisfiable.
| Rich Felker | 2014-06-16 | 1 | -1/+2 |
| * | add sched_{get,set}attr syscall numbers and SCHED_DEADLINE macro•••linux 3.14 introduced sched_getattr and sched_setattr syscalls in
commit d50dde5a10f305253cbc3855307f608f8a3c5f73
and the related SCHED_DEADLINE scheduling policy in
commit aab03e05e8f7e26f51dee792beddcb5cca9215a5
but struct sched_attr "extended scheduling parameters data structure"
is not yet exported to userspace (necessary for using the syscalls)
so related uapi definitions are not added yet.
| Szabolcs Nagy | 2014-05-30 | 1 | -0/+4 |
| * | fix arm thread-pointer/atomic asm when compiling to thumb code•••armv7/thumb2 provides a way to do atomics in thumb mode, but for armv6
we need a call to arm mode.
this commit is based on a patch by Stephen Thomas which fixed the
armv7 cases but not the armv6 ones.
all of this should be revisited if/when runtime selection of thread
pointer access and atomics are added.
| Rich Felker | 2014-04-30 | 2 | -6/+7 |
| * | fix RLIMIT_ constants for mips•••The mips arch is special in that it uses different RLIMIT_
numbers than other archs, so allow bits/resource.h to override
the default RLIMIT_ numbers (empty on all archs except mips).
Reported by orc.
| Szabolcs Nagy | 2014-04-15 | 1 | -0/+0 |
| * | use dmb barrier instruction for atomics on arm v7•••aside from potentially offering better performance, this change is
needed since the old coprocessor-based approach to barriers is
deprecated in arm v7, and some compilers/assemblers issue errors when
using the deprecated instruction for v7 targets.
| Rich Felker | 2014-04-14 | 1 | -2/+9 |
| * | fix arm atomic asm register constraint•••the "m" constraint could give a memory reference with an offset that's
not compatible with ldrex/strex, so the arm-specific "Q" constraint is
needed instead.
| Rich Felker | 2014-04-07 | 1 | -1/+1 |
| * | use inline atomics and thread pointer on arm models supporting them•••this is perhaps not the optimal implementation; a_cas still compiles
to nested loops due to the different interface contracts of the kuser
helper cas function (whose contract this patch implements) and the
a_cas function (whose contract mimics the x86 cmpxchg). fixing this
may be possible, but it's more complicated and thus deferred until a
later time.
aside from improving performance and code size, this patch also
provides a means of producing binaries which can run on hardened
kernels where the kuser helpers have been disabled. however, at
present this requires producing binaries for armv6k or later, which
will not run on older cpus. a real solution to the problem of kernels
that omit the kuser helpers would be runtime detection, so that
universal binaries which run on all arm cpu models can also be
compatible with all kernel hardening profiles. robust detection
however is a much harder problem, and will be addressed at a later
time.
| Rich Felker | 2014-04-07 | 2 | -1/+36 |
| * | fix signal.h breakage from moving stack_t to arch-specific bits•••in the previous changes, I missed the fact that both the prototype of
the sigaltstack function and the definition of ucontext_t depend on
stack_t.
| Rich Felker | 2014-03-18 | 1 | -6/+6 |
| * | move signal.h definition of stack_t to arch-specific bits•••it's different at least on mips. mips version will be fixed in a
separate commit to show the change.
| Rich Felker | 2014-03-18 | 1 | -0/+6 |
| * | move struct semid_ds to from shared sys/sem.h to bits•••the definition was found to be incorrect at least for powerpc, and
fixing this cleanly requires making the definition arch-specific. this
will allow cleaning up the definition for other archs to make it more
specific, and reversing some of the ugliness (time_t hacks) introduced
with the x32 port.
this first commit simply copies the existing definition to each arch
without any changes. this is intentional, to make it easier to review
changes made on a per-arch basis.
| Rich Felker | 2014-03-11 | 1 | -0/+16 |
| * | fixup general __syscall breakage introduced in x32 port•••the reordering of headers caused some risc archs to not see
the __syscall declaration anymore.
this caused build errors on mips with any compiler,
and on arm and microblaze with clang.
we now declare it locally just like the powerpc port does.
| rofl0r | 2014-02-24 | 1 | -0/+2 |
| * | sys/shm.h: move arch specific structs to bits/ | rofl0r | 2014-02-23 | 1 | -0/+11 |
| * | add IUTF8 to termios.h on archs that were missing it | Rich Felker | 2014-01-08 | 1 | -0/+1 |
| * | fix namespace violations in termios.h, at least mostly•••the fix should be complete on archs that use the generic definitions
(i386, arm, x86_64, microblaze), but mips and powerpc have not been
checked thoroughly and may need more fixes.
| Rich Felker | 2014-01-08 | 1 | -8/+7 |
| * | add O_TMPFILE flag, new in linux 3.11•••definition in linux:
#define O_TMPFILE (__O_TMPFILE | O_DIRECTORY)
where __O_TMPFILE and O_DIRECTORY are arch specific
| Szabolcs Nagy | 2013-11-23 | 1 | -0/+1 |
| * | fix the nominal type of LDBL_* limits on archs with ld64•••previously these macros wrongly had type double rather than long
double. I see no way an application could detect the error in C99, but
C11's _Generic can trivially detect it.
at the same time, even though these archs do not have excess
precision, the number of decimal places used to represent these
constants has been increased to 21 to be consistent with the decimal
representations used for the DBL_* macros.
| Rich Felker | 2013-11-20 | 1 | -4/+4 |
| * | fix arm atomic store and generate simpler/less-bloated/faster code•••atomic store was lacking a barrier, which was fine for legacy arm with
no real smp and kernel-emulated cas, but unsuitable for more modern
systems. the kernel provides another "kuser" function, at 0xffff0fa0,
which could be used for the barrier, but using that would drop support
for kernels 2.6.12 through 2.6.14 unless an extra conditional were
added to check for barrier availability. just using the barrier in the
kernel cas is easier, and, based on my reading of the assembly code in
the kernel, does not appear to be significantly slower.
at the same time, other atomic operations are adapted to call the
kernel cas function directly rather than using a_cas; due to small
differences in their interface contracts, this makes the generated
code much simpler.
| Rich Felker | 2013-09-22 | 1 | -6/+8 |
| * | fix detection of arm hardfloat•••it turns out that __SOFTFP__ does not indicate the ABI in use but
rather that fpu instructions are not to be used at all. this is
specified in ARM's documentation so I'm unclear on how I previously
got the wrong idea. unfortunately, this resulted in the 0.9.12 release
producing a dynamic linker with the wrong name. fortunately, there do
not yet seem to be any public toolchain builds using the wrong name.
the __ARM_PCS_VFP macro does not seem to be official from ARM, and in
fact it was missing from the very earliest gcc versions (around 4.5.x)
that added -mfloat-abi=hard. it would be possible on such versions to
perform some ugly linker-based tests instead in hopes that the linker
will reject ABI-mismatching object files, if there is demand for
supporting such versions. I would probably prefer to document which
versions are broken and warn users to manually add -D__ARM_PCS_VFP if
using such a version.
there's definitely an argument to be made that the fenv macros should
be exposed even in -mfloat-abi=softfp mode. for now, I have chosen not
to expose them in this case, since the math library will not
necessarily have the capability to raise exceptions (it depends on the
CFLAGS used to compile it), and since exceptions are officially
excluded from the ARM EABI, which the plain "arm" arch aims to
follow.
| Rich Felker | 2013-08-16 | 1 | -1/+1 |
| * | support floating point environment (fenv) on armhf (hard float) subarchs•••patch by nsz. I've tested it on an armhf machine and it seems to be
working correctly.
| Rich Felker | 2013-08-16 | 1 | -0/+13 |
| * | add function types to arm crt assembly•••without these, calls may be resolved incorrectly if the calling code
has been compiled to thumb instead of arm. it's not clear to me at
this point whether crt_arch.h is even working if crt1.c is built as
thumb; this needs testing. but the _init and _fini issues were known
to cause crashes in static-linked apps when libc was built as thumb,
and this commit should fix that issue.
| Rich Felker | 2013-08-15 | 1 | -0/+1 |
| * | add missing a_or_l to atomic.h for non-x86 archs•••this is needed for recently committed sigaction code
| Rich Felker | 2013-08-11 | 1 | -0/+5 |
| * | new mostly-C crt1 implementation•••the only immediate effect of this commit is enabling PIE support on
some archs that did not previously have any Scrt1.s, since the
existing asm files for crt1 override this C code. so some of the
crt_arch.h files committed are only there for the sake of documenting
what their archs "would do" if they used the new C-based crt1.
the expectation is that new archs should use this new system rather
than using heavy asm for crt1. aside from being easier and less
error-prone, it also ensures that PIE support is available immediately
(since Scrt1.o is generated from the same C source, using -fPIC)
rather than having to be added as an afterthought in the porting
process.
| Rich Felker | 2013-07-26 | 1 | -0/+9 |
| * | change jmp_buf to share an underlying type and struct tag with sigjmp_buf•••this is necessary to meet the C++ ABI target. alternatives were
considered to avoid the size increase for non-sig jmp_buf objects, but
they seemed to have worse properties. moreover, the relative size
increase is only extreme on x86[_64]; one way of interpreting this is
that, if the size increase from this patch makes jmp_buf use too much
memory, then the program was already using too much memory when built
for non-x86 archs.
| Rich Felker | 2013-07-24 | 1 | -1/+1 |
| * | remove SIG_ATOMIC_MIN/MAX from stdint bits headers•••i386 was done with the big commit but I missed the others
| Rich Felker | 2013-07-22 | 1 | -2/+0 |
| * | fix regression in size of nlink_t (broken stat struct) on x86_64•••rather than moving nlink_t back to the arch-specific file, I've added
a macro _Reg defined to the canonical type for register-size values on
the arch. this is not the same as _Addr for (not-yet-supported)
32-on-64 pseudo-archs like x32 and mips n32, so a new macro was
needed.
| Rich Felker | 2013-07-22 | 1 | -0/+1 |
| * | disable legacy init/fini processing on ARM•••since the old, poorly-thought-out musl approach to init/fini arrays on
ARM (when it was the only arch that needed them) was to put the code
in crti/crtn and have the legacy _init/_fini code run the arrays,
adding proper init/fini array support caused the arrays to get
processed twice on ARM. I'm not sure skipping legacy init/fini
processing is the best solution to the problem, but it works, and it
shouldn't break anything since the legacy init/fini system was never
used for ARM EABI.
| Rich Felker | 2013-07-22 | 1 | -0/+2 |
| * | change wint_t to unsigned•••aside from the obvious C++ ABI purpose for this change, it also brings
musl into alignment with the compiler's idea of the definition of
wint_t (use in -Wformat), and makes the situation less awkward on ARM,
where wchar_t is unsigned.
internal code using wint_t and WEOF was checked against this change,
and while a few cases of storing WEOF into wchar_t were found, they
all seem to operate properly with the natural conversion from unsigned
to signed.
| Rich Felker | 2013-07-22 | 1 | -1/+1 |
| * | refactor headers, especially alltypes.h, and improve C++ ABI compat•••the arch-specific bits/alltypes.h.sh has been replaced with a generic
alltypes.h.in and minimal arch-specific bits/alltypes.h.in.
this commit is intended to have no functional changes except:
- exposing additional symbols that POSIX allows but does not require
- changing the C++ name mangling for some types
- fixing the signedness of blksize_t on powerpc (POSIX requires signed)
- fixing the limit macros for sig_atomic_t on x86_64
- making dev_t an unsigned type (ABI matching goal, and more logical)
in addition, some types that were wrongly defined with long on 32-bit
archs were changed to int, and vice versa; this change is
non-functional except for the possibility of making pointer types
mismatch, and only affects programs that were using them incorrectly,
and only at build-time, not runtime.
the following changes were made in the interest of moving
non-arch-specific types out of the alltypes system and into the
headers they're associated with, and also will tend to improve
application compatibility:
- netdb.h now includes netinet/in.h (for socklen_t and uint32_t)
- netinet/in.h now includes sys/socket.h and inttypes.h
- sys/resource.h now includes sys/time.h (for struct timeval)
- sys/wait.h now includes signal.h (for siginfo_t)
- langinfo.h now includes nl_types.h (for nl_item)
for the types in stdint.h:
- types which are of no interest to other headers were moved out of
the alltypes system.
- fast types for 8- and 64-bit are hard-coded (at least for now); only
the 16- and 32-bit ones have reason to vary by arch.
and the following types have been changed for C++ ABI purposes;
- mbstate_t now has a struct tag, __mbstate_t
- FILE's struct tag has been changed to _IO_FILE
- DIR's struct tag has been changed to __dirstream
- locale_t's struct tag has been changed to __locale_struct
- pthread_t is defined as unsigned long in C++ mode only
- fpos_t now has a struct tag, _G_fpos64_t
- fsid_t's struct tag has been changed to __fsid_t
- idtype_t has been made an enum type (also required by POSIX)
- nl_catd has been changed from long to void *
- siginfo_t's struct tag has been removed
- sigset_t's has been given a struct tag, __sigset_t
- stack_t has been given a struct tag, sigaltstack
- suseconds_t has been changed to long on 32-bit archs
- [u]intptr_t have been changed from long to int rank on 32-bit archs
- dev_t has been made unsigned
summary of tests that have been performed against these changes:
- nsz's libc-test (diff -u before and after)
- C++ ABI check symbol dump (diff -u before, after, glibc)
- grepped for __NEED, made sure types needed are still in alltypes
- built gcc 3.4.6
| Rich Felker | 2013-07-22 | 3 | -133/+27 |
| * | change uid_t, gid_t, and id_t to unsigned types•••this change is both to fix one of the remaining type (and thus C++
ABI) mismatches with glibc/LSB and to allow use of the full range of
uid and gid values, if so desired.
passwd/group access functions were not prepared to deal with unsigned
values, so they too have been fixed with this commit.
| Rich Felker | 2013-07-19 | 1 | -3/+3 |
| * | make the dynamic linker find its path file relative to its own location•••prior to this change, using a non-default syslibdir was impractical on
systems where the ordinary library paths contain musl-incompatible
library files. the file containing search paths was always taken from
/etc, which would either correspond to a system-wide musl
installation, or fail to exist at all, resulting in searching of the
default library path.
the new search strategy is safe even for suid programs because the
pathname used comes from the PT_INTERP header of the program being
run, rather than any external input.
as part of this change, I have also begun differentiating the names of
arch variants that differ by endianness or floating point calling
convention. the corresponding changes in the build system and and gcc
wrapper script (to use an alternate dynamic linker name) for these
configurations have not yet been made.
| Rich Felker | 2013-07-18 | 1 | -1/+14 |
| * | add some ARM EABI-specific exception handling infrastructure•••patch by Timo Teräs
| Rich Felker | 2013-07-10 | 1 | -0/+42 |
| * | respect iso c namespace in stdio.h and wchar.h regarding va_list•••despite declaring functions that take arguments of type va_list, these
headers are not permitted by the c standard to expose the definition
of va_list, so an alias for the type must be used. the name
__isoc_va_list was chosen to convey that the purpose of this alternate
name is for iso c conformance, and to avoid the multitude of names
which gcc mangles with its hideous "fixincludes" monstrosity, leading
to serious header breakage if these "fixes" are run.
| Rich Felker | 2013-06-25 | 1 | -0/+1 |
| * | Merge remote-tracking branch 'nsz/review' | Rich Felker | 2013-05-26 | 1 | -3/+3 |
| |\ |
|
| | * | fix ioctl _IOR, _IOW, etc macros to avoid signed overflow (2<<30) | Szabolcs Nagy | 2013-05-26 | 1 | -3/+3 |
| * | | change underlying type of clock_t to be uniform and match ABI•••previously we were using an unsigned type on 32-bit systems so that
subtraction would be well-defined when it wrapped, but since wrapping
is non-conforming anyway (when clock() overflows, it has to return -1)
the only use of unsigned would be to buy a little bit more time before
overflow. this does not seem worth having the type vary per-arch
(which leads to more arch-specific bugs) or disagree with the ABI musl
(mostly) follows.
| Rich Felker | 2013-05-23 | 1 | -1/+1 |
| |/ |
|
| * | add FLT_TRUE_MIN, etc. macros from C11•••there was some question as to how many decimal places to use, since
one decimal place is always sufficient to identify the smallest
denormal uniquely. for now, I'm following the example in the C
standard which is consistent with the other min/max macros we already
had in place.
| Rich Felker | 2013-05-17 | 1 | -0/+1 |
| * | fix type issues in stdint.h so underlying types of 64-bit types match ABI | Rich Felker | 2013-04-04 | 1 | -0/+3 |
| * | eliminate bits/wchar.h•••the preprocessor can reliably determine the signedness of wchar_t.
L'\0' is used for 0 in the expressions so that, if the underlying type
of wchar_t is long rather than int, the promoted type of the
expression will match the type of wchar_t.
| Rich Felker | 2013-04-04 | 1 | -4/+0 |
| * | re-add useconds_t•••this type was removed back in 5243e5f1606a9c6fcf01414e ,
because it was removed from the XSI specs.
however some apps use it.
since it's in the POSIX reserved namespace, we can expose it
unconditionally.
| rofl0r | 2013-04-02 | 1 | -0/+1 |
| * | add syscall numbers for the new kcmp and finit_module syscalls•••and remove syscall todos from microblaze
| Szabolcs Nagy | 2013-04-01 | 1 | -0/+4 |
