musl/src/thread/microblaze, branch v1.2.0 musl - an implementation of the standard library for Linux-based systems make arch __set_thread_area backends hidden 2018-09-12T18:34:32+00:00 Rich Felker dalias@aerifal.cx 2018-09-10T19:42:03+00:00 5e1019b01c968707accc85c99e63a18af665cf27 this is not a public interface, and does not even necessarily match the syscall on all archs that have a syscall by that name. on archs where it's implemented in C, no action on the source file is needed; the hidden declaration in pthread_arch.h suffices. 
this is not a public interface, and does not even necessarily match
the syscall on all archs that have a syscall by that name.

on archs where it's implemented in C, no action on the source file is
needed; the hidden declaration in pthread_arch.h suffices.
make arch __clone backends hidden 2018-09-12T18:34:31+00:00 Rich Felker dalias@aerifal.cx 2018-09-10T19:36:33+00:00 f5f7673d71f843b423e60bbdd7de49fd1bbcc8c1 these are not a public interface and are not intended to be callable from anywhere but the public clone function or other places in libc. 
these are not a public interface and are not intended to be callable
from anywhere but the public clone function or other places in libc.
use explicit __cp_cancel label in cancellable syscall asm for all archs 2015-11-02T21:16:00+00:00 Rich Felker dalias@aerifal.cx 2015-11-02T21:16:00+00:00 36e8b6a28be5d4ffad966386b1e1c0d0dc6ca11a previously, only archs that needed to do stack cleanup defined a __cp_cancel label for acting on cancellation in their syscall asm, and a default definition was provided by a weak alias to __cancel, the C function. this resulted in wrong codegen for arm on gcc versions affected by pr 68178 and possibly similar issues (like pr 66609) on other archs, and also created an inconsistency where the __cp_begin and __cp_end labels were treated as const data but __cp_cancel was treated as a function. this in turn caused incorrect code generation on archs where function pointers point to function descriptors rather than code (for now, only sh/fdpic). 
previously, only archs that needed to do stack cleanup defined a
__cp_cancel label for acting on cancellation in their syscall asm, and
a default definition was provided by a weak alias to __cancel, the C
function. this resulted in wrong codegen for arm on gcc versions
affected by pr 68178 and possibly similar issues (like pr 66609) on
other archs, and also created an inconsistency where the __cp_begin
and __cp_end labels were treated as const data but __cp_cancel was
treated as a function. this in turn caused incorrect code generation
on archs where function pointers point to function descriptors rather
than code (for now, only sh/fdpic).
consistently use hidden visibility for cancellable syscall internals 2015-04-14T15:18:59+00:00 Rich Felker dalias@aerifal.cx 2015-04-14T15:18:59+00:00 cbc02ba23cec16d7a821648ea8424546bc7f02dc in a few places, non-hidden symbols were referenced from asm in ways that assumed ld-time binding. while these is no semantic reason these symbols need to be hidden, fixing the references without making them hidden was going to be ugly, and hidden reduces some bloat anyway. in the asm files, .global/.hidden directives have been moved to the top to unclutter the actual code. 
in a few places, non-hidden symbols were referenced from asm in ways
that assumed ld-time binding. while these is no semantic reason these
symbols need to be hidden, fixing the references without making them
hidden was going to be ugly, and hidden reduces some bloat anyway.

in the asm files, .global/.hidden directives have been moved to the
top to unclutter the actual code.
clone: make clone a wrapper around __clone 2014-02-10T02:07:43+00:00 Bobby Bingham koorogi@koorogi.info 2014-02-07T04:11:22+00:00 fdf5f1b13123883ac1d5e298e5f32c7ed43578ce The architecture-specific assembly versions of clone did not set errno on failure, which is inconsistent with glibc. __clone still returns the error via its return value, and clone is now a wrapper that sets errno as needed. The public clone has also been moved to src/linux, as it's not directly related to the pthreads API. __clone is called by pthread_create, which does not report errors via errno. Though not strictly necessary, it's nice to avoid clobbering errno here. 
The architecture-specific assembly versions of clone did not set errno on
failure, which is inconsistent with glibc.  __clone still returns the error
via its return value, and clone is now a wrapper that sets errno as needed.
The public clone has also been moved to src/linux, as it's not directly
related to the pthreads API.

__clone is called by pthread_create, which does not report errors via
errno.  Though not strictly necessary, it's nice to avoid clobbering errno
here.
fix order of syscall args for microblaze clone syscall 2012-10-19T04:27:03+00:00 Rich Felker dalias@aerifal.cx 2012-10-19T04:27:03+00:00 6a04d1b8c6181eebfc1d99c6b0e190728d4fabf1 with this commit, based on testing with patches to qemu which are not yet upstream, 
with this commit, based on testing with patches to qemu which are not
yet upstream,
ensure microblaze __set_thread_area returns success 2012-10-19T02:01:24+00:00 Rich Felker dalias@aerifal.cx 2012-10-19T02:01:24+00:00 1f485230df7a1c634fcec29d870d2566aee2031c since it did not set the return-value register, the caller could wrongly interpret this as failure. 
since it did not set the return-value register, the caller could
wrongly interpret this as failure.
fix microblaze asm relocations for shared libc 2012-10-18T03:45:21+00:00 Rich Felker dalias@aerifal.cx 2012-10-18T03:45:21+00:00 ef2f595f7489a79b328766e3f8c2c899c8d23fd1 only @PLT relocations are considered functions for purposes of -Bsymbolic-functions, so always use @PLT. it should not hurt in the static-linked case. 
only @PLT relocations are considered functions for purposes of
-Bsymbolic-functions, so always use @PLT. it should not hurt in the
static-linked case.
microblaze port 2012-09-29T05:05:31+00:00 Rich Felker dalias@aerifal.cx 2012-09-29T05:05:31+00:00 8c0a3d9e5c169fc9d0f246ab59362b658b029ad7 based on initial work by rdp, with heavy modifications. some features including threads are untested because qemu app-level emulation seems to be broken and I do not have a proper system image for testing. 
based on initial work by rdp, with heavy modifications. some features
including threads are untested because qemu app-level emulation seems
to be broken and I do not have a proper system image for testing.