public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "omar beo" <omarbeo@hotmail.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/10772: Result differences between debug and optmize libs on linux; and with sol/nt on optimize mode
Date: Wed, 14 May 2003 19:26:00 -0000	[thread overview]
Message-ID: <20030514192602.16589.qmail@sources.redhat.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2476 bytes --]

The following reply was made to PR optimization/10772; it has been noted by GNATS.

From: "omar beo" <omarbeo@hotmail.com>
To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, omarbeo@hotmail.com, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: optimization/10772: Result differences between debug and optmize libs on
 linux; and with sol/nt on optimize mode
Date: Wed, 14 May 2003 13:20:26 -0600

 Hi,
 I tried your suggestion, and build the libs using " -ffloat-store " flag.
 It is true that now "Optimized and debug compilations give the same result 
 on Linux".
 But this did not answer the original question, why I’m not getting the same 
 results in the other platforms?
 
 If you run the test I provided, you will see that the result should be 
 00005975 in every case, but it is not when i run on linux. Why?
 
 If you are getting the same number in every case, could you please send me 
 the compilation arguments you used?
 
 The results of the test:
 Linux: debug or optimize libs
 var_1: 00005975
 var_2: 00005974  ...... * should be 00005974
 var_3: 00005975
 var_4: 00005974  .........* should be 00005974
 var_5: 00005975
 
 While sol debug or optimize give:
 var_1: 00005975
 var_2: 00005975
 var_3: 00005975
 var_4: 00005975
 var_5: 00005975
 
 
 >From: bangerth@dealii.org
 >Reply-To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,  
 >nobody@gcc.gnu.org, omarbeo@hotmail.com, gcc-gnats@gcc.gnu.org
 >To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,  
 >omarbeo@hotmail.com
 >Subject: Re: optimization/10772: Result differences between debug and 
 >optmize libs on linux; and with sol/nt on optimize mode
 >Date: 14 May 2003 15:14:49 -0000
 >
 >Synopsis: Result differences between debug and optmize libs on linux; and 
 >with sol/nt on optimize mode
 >
 >State-Changed-From-To: feedback->closed
 >State-Changed-By: bangerth
 >State-Changed-When: Wed May 14 15:14:48 2003
 >State-Changed-Why:
 >     Not a bug. Optimized and debug compilations give the same
 >     result is -ffloat-store is used. On NT, a similar accuracy
 >     truncation mechanism is used by default. On Solaris, all
 >     accuracy is 64bit.
 >
 >     W.
 >
 >http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10772
 
 _________________________________________________________________
 STOP MORE SPAM with the new MSN 8 and get 2 months FREE*  
 http://join.msn.com/?page=features/junkmail
 


             reply	other threads:[~2003-05-14 19:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-14 19:26 omar beo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-14 20:56 Wolfgang Bangerth
2003-05-14 15:16 omar beo
2003-05-14 15:14 bangerth
2003-05-14 14:36 Christian Ehrhardt
2003-05-14 10:48 giovannibajo
2003-05-14  6:26 Dara Hazeghi
2003-05-13 18:26 omarbeo

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=20030514192602.16589.qmail@sources.redhat.com \
    --to=omarbeo@hotmail.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).