riscv/musl - musl - Gitea: Git with a cup of tea

Author	SHA1	Message	Date
Rich Felker	0ed932f34f	do not define static_assert macro for pre-C11 compilers some software simply uses static_assert if the macro is defined, and this breaks if the compiler does not recognize the _Static_assert keyword used to define it.	10 years ago
Szabolcs Nagy	70729de075	add static_assert and hide noreturn, alignas, alignof from C++ add static_assert and protect the other new C11 keyword macros with #ifndef __cplusplus so they don't conflict with C++ keywords.	12 years ago
rofl0r	2c1f8fd5da	__assert_fail(): remove _Noreturn, to get proper stacktraces for _Noreturn functions, gcc generates code that trashes the stack frame, and so it makes it impossible to inspect the causes of an assert error in gdb. abort() is not affected (i have not yet investigated why).	14 years ago
Rich Felker	858df113bf	assert() is supposed to have type void	14 years ago
Rich Felker	c1a9658bd1	default features: make musl usable without feature test macros the old behavior of exposing nothing except plain ISO C can be obtained by defining __STRICT_ANSI__ or using a compiler option (such as -std=c99) that predefines it. the new default featureset is POSIX with XSI plus _BSD_SOURCE. any explicit feature test macros will inhibit the default. installation docs have also been updated to reflect this change.	14 years ago
Rich Felker	0c05bd3a9c	further use of _Noreturn, for non-plain-C functions note that POSIX does not specify these functions as _Noreturn, because POSIX is aligned with C99, not the new C11 standard. when POSIX is eventually updated to C11, it will almost surely give these functions the _Noreturn attribute. for now, the actual _Noreturn keyword is not used anyway when compiling with a c99 compiler, which is what POSIX requires; the GCC __attribute__ is used instead if it's available, however. in a few places, I've added infinite for loops at the end of _Noreturn functions to silence compiler warnings. presumably __buildin_unreachable could achieve the same thing, but it would only work on newer GCCs and would not be portable. the loops should have near-zero code size cost anyway. like the previous _Noreturn commit, this one is based on patches contributed by philomath.	14 years ago
Rich Felker	0b44a0315b	initial check-in, version 0.5.0	15 years ago