Tree: 2b43ef8fc7

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 '2b43ef8fc7'

${ noResults }

Commit Graph

2 Commits (2b43ef8fc76eaf3912aa98316eae82797494276d)

Author	SHA1	Message	Date
Rich Felker	ad2fe25041	support the ugly and deprecated ucontext and sigcontext header stuff... only the structures, not the functions from ucontext.h, are supported at this point. the main goal of this commit is to make modern gcc with dwarf2 unwinding build without errors. honestly, it probably doesn't matter how we define these as long as they have members with the right names to prevent errors while compiling libgcc. the only time they will be used is for propagating exceptions across signal-handler boundaries, which invokes undefined behavior anyway. but as-is, they're probably correct and may be useful to various low-level applications dealing with virtualization, jit code generation, and so on...	15 years ago
Rich Felker	1355fdca7c	preparing build system to handle ports - step 1	15 years ago
Rich Felker	1322cb82a3	header cleanup, conformance fixes - signals	15 years ago
Rich Felker	e1d8d25a50	fix omission that kept sa_restorer from being used	15 years ago
Rich Felker	0b44a0315b	initial check-in, version 0.5.0	15 years ago