public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ghazi at caip dot rutgers dot edu" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug math/10401] cproj(3) does a different projection than expected
Date: Wed, 07 Apr 2010 15:07:00 -0000	[thread overview]
Message-ID: <20100407150705.27336.qmail@sourceware.org> (raw)
In-Reply-To: <20090716111020.10401.ekamperi@gmail.com>


------- Additional Comments From ghazi at caip dot rutgers dot edu  2010-04-07 15:07 -------
Any progress on fixing this?  I'm going to make GCC's __builtin_cproj optimize 
according to the standard C definition.  I'd like GCC and GLIBC to have the 
same (standard/correct) implementation.  Thanks.



-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ghazi at caip dot rutgers
                   |                            |dot edu


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

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  reply	other threads:[~2010-04-07 15:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-16 11:10 [Bug math/10401] New: " ekamperi at gmail dot com
2010-04-07 15:07 ` ghazi at caip dot rutgers dot edu [this message]
2010-04-08 22:33 ` [Bug math/10401] " drepper at redhat dot com
     [not found] <bug-10401-131@http.sourceware.org/bugzilla/>
2014-02-16 17:45 ` jackie.rosen at hushmail dot com
2014-05-28 19:44 ` schwab at sourceware dot org
2014-07-01  7:48 ` fweimer at redhat dot com
2021-08-19  6:03 ` ucelsanicin at yahoo dot com
2021-09-10 19:36 ` mehmetgelisin at aol dot com
2021-09-10 19:51 ` mark at klomp dot org
2021-09-15  2:38 ` namboru at jasaseo dot one

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=20100407150705.27336.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.com \
    /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).