public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/32391] Wrong code with optimization on i686-pc-linux-gnu
Date: Thu, 21 Jun 2007 02:24:00 -0000	[thread overview]
Message-ID: <20070621022431.14250.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32391-14714@http.gcc.gnu.org/bugzilla/>



------- Comment #17 from kargl at gcc dot gnu dot org  2007-06-21 02:24 -------
(In reply to comment #16)
> Thank all of you.
> I could understand what make it different.
> 
> There is no 'volatile' statement in fortran77 syntax of gfortran.
> Of course, volatile is not fortran77 standard, I think,
> but a certian implimentation support volatile.

You need to update the Fortran Standard that you use.  Fortran
77 hasn't been the standard since about 1990.  In fact, you're
3 standard been!  There was Fortran 90, which was replaced by
Fortran 95, which was replaced by Fortran 2003.  Fortran 2003 
has the VOLATILE attribute and VOLATILE statement.  Guess what??
No, go ahead and guess!  gfortran supports this feature.

You need to go read Goldberg's paper about floating point arithmetic.


-- 


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


  parent reply	other threads:[~2007-06-21  2:24 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-18 14:12 [Bug fortran/32391] New: Default optimization (level 1) bug of loop optimization (maybe) sunjoong at gmail dot com
2007-06-18 14:19 ` [Bug fortran/32391] " sunjoong at gmail dot com
2007-06-18 14:19 ` sunjoong at gmail dot com
2007-06-18 14:20 ` sunjoong at gmail dot com
2007-06-18 15:08 ` [Bug fortran/32391] Generate wrong optimization code from fortran 77 sunjoong at gmail dot com
2007-06-18 15:38 ` [Bug fortran/32391] Generate wrong optimization code on " dominiq at lps dot ens dot fr
2007-06-18 16:07 ` sunjoong at gmail dot com
2007-06-18 16:38 ` [Bug fortran/32391] Wrong code with optimization on i686-pc-linux-gnu burnus at gcc dot gnu dot org
2007-06-18 17:26 ` sunjoong at gmail dot com
2007-06-18 18:31 ` sunjoong at gmail dot com
2007-06-18 18:36 ` kargl at gcc dot gnu dot org
2007-06-18 18:47 ` sunjoong at gmail dot com
2007-06-18 19:16 ` kargl at gcc dot gnu dot org
2007-06-18 20:24 ` sunjoong at gmail dot com
2007-06-18 20:48 ` kargl at gcc dot gnu dot org
2007-06-19  8:11 ` pinskia at gcc dot gnu dot org
2007-06-20 23:34 ` sunjoong at gmail dot com
2007-06-21  2:24 ` kargl at gcc dot gnu dot org [this message]
2007-06-21  3:27 ` sunjoong at gmail dot com
2007-06-21  4:08 ` kargl at gcc dot gnu dot org
2007-06-21  4:35 ` sunjoong at gmail dot com
2007-06-21  4:55 ` kargl at gcc dot gnu dot org
2007-06-21  9:15 ` sunjoong at gmail 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=20070621022431.14250.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).