Remove __wur from setfsuid and setfsgid.
ARM: Macroize assembly use of EABI unwind directives.
Russian translations update.

	* po/ru.po: Update Russion translation from translation project.
Minor cleanup in getaddrinfo

Replace repeated computations of alloca size with a local variable
that stores the computed value.
Consolidate pthread_attr value validation

Define inline functions that wrap around validation for each of the
pthread attributes to reduce duplication in code.
Fix getent to call endspent rather than endpwent for shadow database.
S/390: Change struct statfs[64] member types to unsigned values

Kay Sievers reported that coreutils' stat tool has a problem with
s390's statfs[64] definition:

> The definition of struct statfs::f_type needs a fix. s390 is the only
> architecture in the kernel that uses an int and expects magic
> constants lager than INT_MAX to fit into.
>
> A fix is needed to make Fedora boot on s390, it currently fails to do
> so. Userspace does not want to add code to paper-over this issue.

[...]

> Even coreutils cannot handle it:
>   #define RAMFS_MAGIC  0x858458f6
>   # stat -f -c%t /
>   ffffffff858458f6
>
>   #define BTRFS_SUPER_MAGIC 0x9123683E
>   # stat -f -c%t /mnt
>   ffffffff9123683e

The bug is caused by an implicit sign extension within the stat tool:

out_uint_x (pformat, prefix_len, statfsbuf->f_type);

where the format finally will be "%lx".
A similar problem can be found in the 'tail' tool.
s390 is the only architecture which has an int type f_type member in
struct statfs[64]. Other architectures have either unsigned ints or
long values, so that the problem doesn't occur there.

Therefore change the type of the f_type member to unsigned int, so
that we get zero extension instead sign extension when assignment to
a long value happens.

Reported-by: Kay Sievers <kay@vrfy.org>
Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>
Remove non-standard initialisation of flexible array member

This avoids GCC bug 28865.
Consistently use ISSPACE to check for whitespace

Resolves #14888.

This only really manifests itself when there are no spaces between
format specifiers, which is not allowed by POSIX, but is allowed by
the glibc implementation.
PowerPC: modf optimization

This patch implements modf/modff optimization for POWER by focus
on FP operations instead of relying in integer ones.
Add generic POSIX implementation of C11 timespec_get.
Fix name space use in last commit.
Mention files in which fast/slow paths of math functions are implemented
Fix catan, catanh inaccuracy through use of log (bug 15394).
Use suffixed floating-point constants in float and long double catan/catanh.
Add catan, catanh tests at +/- 1 and +/- i.
math: Use accurate answers for cos and sincos.

Use the most accurate hex literals possible for the answers to the
cos and sincos tests that vary according to the error in the rounding
of PI/2.

---

2013-04-24  Carlos O'Donell  <carlos@redhat.com>

	* math/libm-test.inc (cos_test): Use accurate hex constants.
	(sincost_test): Likewise.
soft-fp: s/sNAN/NAN/ -- no sNaNs are ever produced.
Declare __ehdr_start with hidden visibility.

This avoids a linker bug triggering for MIPS SVR4 binaries:

http://sourceware.org/bugzilla/show_bug.cgi?id=15365

and regardless serves as a documentation of intent.
Get rid of __STDC_FORMAT_MACROS, __STDC_LIMIT_MACROS and __STDC_CONSTANT_MACROS