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/16918] [arm] feupdateenv (FE_NOMASK_ENV) should check for failure
Date: Tue, 24 Jun 2014 13:59:00 -0000	[thread overview]
Message-ID: <bug-16918-131-dKdRM4NJfd@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16918-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=16918

--- 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  db59bad394ef61bf6d6ef7916012f2a09d0b3d11 (commit)
      from  001f7b773c637560ecfa686452a5e68d60d07db3 (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=db59bad394ef61bf6d6ef7916012f2a09d0b3d11

commit db59bad394ef61bf6d6ef7916012f2a09d0b3d11
Author: Wilco <wdijkstr@arm.com>
Date:   Tue Jun 24 13:53:04 2014 +0000

    Rewrite feupdateenv

    This patch rewrites feupdateenv to improve performance by avoiding
    unnecessary FPSCR reads/writes. It fixes bug 16918 by passing the
    correct return value.

    2014-06-24  Wilco  <wdijkstr@arm.com>

        [BZ #16918]
        * sysdeps/arm/feupdateenv.c (feupdateenv):
        Rewrite to reduce FPSCR accesses and fix return value.

-----------------------------------------------------------------------

Summary of changes:
 ChangeLog                 |    6 ++++++
 sysdeps/arm/feupdateenv.c |   44 ++++++++++++++++++++++++++++++++++++++------
 2 files changed, 44 insertions(+), 6 deletions(-)

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2014-06-24 13:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-06 22:36 [Bug math/16918] New: " jsm28 at gcc dot gnu.org
2014-06-12 19:23 ` [Bug math/16918] " fweimer at redhat dot com
2014-06-24 13:59 ` cvs-commit at gcc dot gnu.org [this message]
2014-06-24 15:13 ` cvs-commit at gcc dot gnu.org
2014-06-24 15:29 ` cvs-commit at gcc dot gnu.org
2014-06-24 15:42 ` cvs-commit at gcc dot gnu.org
2014-06-24 15:47 ` wdijkstr at arm 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-16918-131-dKdRM4NJfd@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: link
Be 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).