public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: pel@ucla.edu To: gcc-gnats@gcc.gnu.org Subject: c++/7369: weird results with the statement "#define PI 4.*atan(1.)" Date: Sun, 21 Jul 2002 12:06:00 -0000 [thread overview] Message-ID: <20020721190344.20561.qmail@sources.redhat.com> (raw) >Number: 7369 >Category: c++ >Synopsis: weird results with the statement "#define PI 4.*atan(1.)" >Confidential: no >Severity: non-critical >Priority: low >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Sun Jul 21 12:06:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Peter Latham >Release: 2.96 >Organization: >Environment: Red Hat Linux 7.3 >Description: If PI is defined via the statement #define PI 4.*atan(1.) then 1/PI and 1/3.14159 are different. >How-To-Repeat: compile using "g++ main.c". then type "a.out", which prints PI, 1/PI and 1/3.14159. the result is 3.141593 0.196350 0.318310 If for some strange reasont the file didn't attach properly, the source code is: #include <stdio.h> #include <math.h> #define PI 4.*atan(1.) //#define PI 3.14159 void main(int argc, char** argv) { fprintf(stdout, "%f %f %f\n", PI, 1/PI, 1/3.14159); } >Fix: the workaround is to not use atan in the define statement, #define PI=3.14159 this produces the correct output. >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: application/octet-stream; name="main.c" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="main.c" CiNpbmNsdWRlIDxzdGRpby5oPgojaW5jbHVkZSA8bWF0aC5oPgoKI2RlZmluZSBQSSA0LiphdGFu KDEuKQovLyNkZWZpbmUgUEkgMy4xNDE1OQoKdm9pZCBtYWluKGludCBhcmdjLCBjaGFyKiogYXJn dikKewoJZnByaW50ZihzdGRvdXQsICIlZiAlZiAlZlxuIiwgUEksIDEvUEksIDEvMy4xNDE1OSk7 Cn0K
next reply other threads:[~2002-07-21 19:06 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-07-21 12:06 pel [this message] 2002-07-21 12:36 Andrew Pinski 2002-07-21 12:46 gdr
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=20020721190344.20561.qmail@sources.redhat.com \ --to=pel@ucla.edu \ --cc=gcc-gnats@gcc.gnu.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).