public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug math/18110] hppa: feholdexcept and fesetenv incorrectly compiled. Date: Wed, 11 Mar 2015 06:29:00 -0000 [thread overview] Message-ID: <bug-18110-131-sOPtu5mYvH@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-18110-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=18110 --- Comment #1 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 e4363cfb5760d88a9f353c69383b15d5c2705070 (commit) via fae1aa8d226ce860124efd67ede03004b19b89e2 (commit) from 068a6274556f9f362443648f4fd47525c8cf2dba (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=e4363cfb5760d88a9f353c69383b15d5c2705070 commit e4363cfb5760d88a9f353c69383b15d5c2705070 Author: Carlos O'Donell <carlos@systemhalted.org> Date: Wed Mar 11 02:42:27 2015 -0400 hppa: Fix feupdateenv and fesetexceptflag (Bug 18111). The function feupdateenv has been fixed to correctly handle FE_DFL_ENV and FE_NOMASK_ENV. The fesetexceptflag function has been fixed to correctly handle setting the new flags instead of just OR-ing the existing flags. This fixes the test-fenv-return and test-fenvinline failures on hppa. https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=fae1aa8d226ce860124efd67ede03004b19b89e2 commit fae1aa8d226ce860124efd67ede03004b19b89e2 Author: John David Anglin <danglin@gcc.gnu.org> Date: Tue Mar 10 23:43:50 2015 -0400 hppa: Fix feholdexcpt and fesetenv (Bug 18110). The constraints in the inline assembly in feholdexcept and fesetenv are incorrect. The assembly modifies the buffer pointer, but doesn't express that in the constraints. The simple fix is to remove the modification of the buffer pointer which is no longer required by the existing code, and adjust the one constraint that did express the modification of bufptr. The change fixes test-fenv when glibc is compiled with recent gcc. ----------------------------------------------------------------------- Summary of changes: ChangeLog | 16 ++++++++++++++++ NEWS | 3 ++- sysdeps/hppa/fpu/feholdexcpt.c | 10 ++++------ sysdeps/hppa/fpu/fesetenv.c | 4 ++-- sysdeps/hppa/fpu/feupdateenv.c | 19 ++++++++++++++++--- sysdeps/hppa/fpu/fpu_control.h | 7 ++++++- sysdeps/hppa/fpu/fsetexcptflg.c | 18 ++++++++++++------ 7 files changed, 58 insertions(+), 19 deletions(-) -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2015-03-11 6:29 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-11 3:38 [Bug math/18110] New: " carlos at redhat dot com 2015-03-11 6:29 ` cvs-commit at gcc dot gnu.org [this message] 2015-03-11 6:30 ` [Bug math/18110] " carlos at redhat dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-18110-131-sOPtu5mYvH@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).