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 build/15985] toolchain building for sparc32 fails
Date: Wed, 06 Nov 2013 21:26:00 -0000	[thread overview]
Message-ID: <bug-15985-131-DmrJqhpMc0@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15985-131@http.sourceware.org/bugzilla/>

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

--- Comment #6 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
       via  8d6bb57c44557c344d56653c3380885bf1dcabd7 (commit)
      from  e256c4214c9484873921d4bdb723b842b5627e42 (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=8d6bb57c44557c344d56653c3380885bf1dcabd7

commit 8d6bb57c44557c344d56653c3380885bf1dcabd7
Author: David S. Miller <davem@davemloft.net>
Date:   Wed Nov 6 13:01:36 2013 -0800

    Fix build on pre-v9 32-bit Sparc.

    We cannot use fnegd in this code, as fnegd was added in v9.
    Only fnegs exists in v8 and earlier.

        [BZ #15985]
        * sysdeps/sparc/sparc32/fpu/s_fdim.S (__fdim): Do not use fnegd
        on pre-v9 cpus, use a fnegs+fmovs sequence instead.

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

Summary of changes:
 ChangeLog                          |    6 ++++++
 NEWS                               |    4 ++--
 sysdeps/sparc/sparc32/fpu/s_fdim.S |    3 ++-
 3 files changed, 10 insertions(+), 3 deletions(-)

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


  parent reply	other threads:[~2013-11-06 21:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-28 14:06 [Bug build/15985] New: " wbx at openadk dot org
2013-09-28 17:51 ` [Bug build/15985] " carlos at redhat dot com
2013-09-29 12:14 ` wbx at openadk dot org
2013-09-30 16:05 ` carlos at redhat dot com
2013-10-26 19:20 ` wbx at openadk dot org
2013-10-26 22:14 ` davem at davemloft dot net
2013-10-26 22:14 ` davem at davemloft dot net
2013-11-06 21:26 ` cvs-commit at gcc dot gnu.org [this message]
2013-11-06 21:38 ` cvs-commit at gcc dot gnu.org
2013-11-06 21:40 ` davem at davemloft dot net
2013-11-07  7:09 ` cvs-commit at gcc dot gnu.org
2014-01-06 16:55 ` cvs-commit at gcc dot gnu.org
2014-01-06 16:56 ` cvs-commit at gcc dot gnu.org
2014-06-13  9:41 ` fweimer 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-15985-131-DmrJqhpMc0@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).