public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "lani at oas dot ca" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/15437] int vs const int computation: different answers
Date: Sat, 15 May 2004 04:28:00 -0000	[thread overview]
Message-ID: <20040514173007.17098.qmail@sourceware.org> (raw)
In-Reply-To: <20040514162247.15437.lani@oas.ca>


------- Additional Comments From lani at oas dot ca  2004-05-14 17:30 -------
Subject: Re:  int vs const int computation: different answers

Okay. Well it may or may not be intended, but if one gives a different answer
than the other, which is totally unexpected as far as I'm concerned, then it's
still a bug. This should not happen. Our company is doing computations where
this kind of thing really matters. However, we have somewhat of a workaround to
use, so I won't pursue the issue any further.

Thanks for responding so promptly though.

Lani

pinskia at gcc dot gnu dot org writes :
> 
> 
> ------- Additional Comments From pinskia at gcc dot gnu dot org  2004-05-14 16:54 -------
> Not a bug, the difference comes from constant prorogation (which is used for the const int case) and on 
> x86 the precission is higher than the normal causing some round off errors to happen, see PR 323 for 
> more information.
> 
> *** This bug has been marked as a duplicate of 323 ***
> 
> -- 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>              Status|UNCONFIRMED                 |RESOLVED
>          Resolution|                            |DUPLICATE
> 
> 
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15437
> 
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
> 



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15437


  parent reply	other threads:[~2004-05-14 17:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-14 21:20 [Bug c/15437] New: " lani at oas dot ca
2004-05-14 22:11 ` [Bug c/15437] " pinskia at gcc dot gnu dot org
2004-05-15  4:28 ` lani at oas dot ca [this message]
2004-05-15 11:39 ` bangerth at dealii dot org
2004-05-15 15:37 ` lani at oas dot ca
2004-05-15 15:50 ` bangerth at dealii dot org
2004-05-15 16:08 ` lani at oas dot ca
2004-05-15 16:42 ` bangerth at dealii dot org
2004-05-15 16:42 ` schwab at suse dot de
2004-05-15 17:09 ` lani at oas dot ca

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=20040514173007.17098.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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: 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).