[Bug libc/24088] VSCR field is not being correctly read in ucontext_t on ppc64le
cvs-commit at gcc dot gnu.org
sourceware-bugzilla@sourceware.org
Fri Jan 11 19:53:00 GMT 2019
https://sourceware.org/bugzilla/show_bug.cgi?id=24088
--- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU C Library master sources".
The branch, master has been updated
via 0bc9bdf159f43c50ec31e9a1670e2e04b5d4060d (commit)
from 5494af04adabe72cbd0055fe9ed466af529eaafd (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=0bc9bdf159f43c50ec31e9a1670e2e04b5d4060d
commit 0bc9bdf159f43c50ec31e9a1670e2e04b5d4060d
Author: Rogerio Alves <rcardoso@linux.ibm.com>
Date: Mon Nov 5 10:18:38 2018 -0600
powerpc: Fix VSCR position in ucontext (bug 24088)
This patch fix VSCR position on ucontext. VSCR was read in the wrong
position on ucontext structure because it was ignoring the machine
endianess.
[BZ #24088]
* sysdeps/unix/sysv/linux/powerpc/sys/ucontext.h (vscr_t): Added
ifdef to fix read of VSCR.
* sysdeps/powerpc/powerpc64/Makefile [$subdir == stdlib]: Add
tst-ucontext-ppc64-vscr.c to test list.
* sysdeps/powerpc/powerpc64/tst-ucontext-ppc64-vscr.c: New test file.
Reviewed-by: Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com>
-----------------------------------------------------------------------
Summary of changes:
ChangeLog | 8 ++
sysdeps/powerpc/powerpc64/Makefile | 5 +
.../powerpc/powerpc64/tst-ucontext-ppc64-vscr.c | 84 ++++++++++++++++++++
sysdeps/unix/sysv/linux/powerpc/sys/ucontext.h | 5 +
4 files changed, 102 insertions(+), 0 deletions(-)
create mode 100644 sysdeps/powerpc/powerpc64/tst-ucontext-ppc64-vscr.c
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the Glibc-bugs
mailing list