You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Tree: 6e2bb7acf4

master

rs-1.0

v0.5.0

v0.5.9

v0.6.0

v0.7.0

v0.7.1

v0.7.10

v0.7.11

v0.7.12

v0.7.5

v0.7.6

v0.7.7

v0.7.8

v0.7.9

v0.8.0

v0.8.1

v0.8.10

v0.8.2

v0.8.3

v0.8.4

v0.8.5

v0.8.6

v0.8.7

v0.8.8

v0.8.9

v0.9.0

v0.9.1

v0.9.10

v0.9.11

v0.9.12

v0.9.13

v0.9.14

v0.9.15

v0.9.2

v0.9.3

v0.9.4

v0.9.5

v0.9.6

v0.9.7

v0.9.8

v0.9.9

v1.0.0

v1.0.1

v1.0.2

v1.0.3

v1.0.4

v1.0.5

v1.1.0

v1.1.1

v1.1.10

v1.1.11

v1.1.12

v1.1.13

v1.1.14

v1.1.15

v1.1.16

v1.1.17

v1.1.18

v1.1.19

v1.1.2

v1.1.20

v1.1.21

v1.1.22

v1.1.23

v1.1.24

v1.1.3

v1.1.4

v1.1.5

v1.1.6

v1.1.7

v1.1.8

v1.1.9

v1.2.0

v1.2.1

v1.2.2

v1.2.3

v1.2.4

v1.2.5

v1.2.6

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '6e2bb7acf4'

${ noResults }

musl/arch/or1k

History

Rich Felker ea818ea834 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.		12 years ago
..
bits	add max_align_t definition for C11 and C++11	12 years ago
atomic.h	add working a_spin() atomic for non-x86 targets	12 years ago
crt_arch.h	add or1k (OpenRISC 1000) architecture port	12 years ago
pthread_arch.h	add or1k (OpenRISC 1000) architecture port	12 years ago
reloc.h	add or1k (OpenRISC 1000) architecture port	12 years ago
syscall_arch.h	fix broken offset argument to the mmap2 syscall on or1k	12 years ago