public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug soft-fp/15667] New: __FP_FRAC_ADD_3 shadowing variables in _FP_MUL_MEAT_2_wide_3mul
Date: Sat, 22 Jun 2013 11:41:00 -0000	[thread overview]
Message-ID: <bug-15667-131@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 15667
           Summary: __FP_FRAC_ADD_3 shadowing variables in
                    _FP_MUL_MEAT_2_wide_3mul
           Product: glibc
           Version: 2.17
            Status: NEW
          Severity: normal
          Priority: P2
         Component: soft-fp
          Assignee: unassigned at sourceware dot org
          Reporter: jsm28 at gcc dot gnu.org
                CC: joseph at codesourcery dot com

The soft-fp macro __FP_FRAC_ADD_3 defines variables _c1 and _c2.  The macro
_FP_MUL_MEAT_2_wide_3mul defines its own variables with those names and calls
__FP_FRAC_ADD_3 with arguments involving them, yielding erroneous results when
the wrong variables get used.

(I don't think this actually affects the current uses of soft-fp in glibc on
any architecture; it came up while testing a patch adding new uses.  But it
seems appropriate to file this in Bugzilla anyway.)

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


             reply	other threads:[~2013-06-22 11:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-22 11:41 jsm28 at gcc dot gnu.org [this message]
2013-06-22 19:28 ` [Bug soft-fp/15667] " jsm28 at gcc dot gnu.org
2014-06-13 17:30 ` 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-15667-131@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).