public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/100855] pow run time gfortran vs ifort Date: Sat, 05 Jun 2021 11:59:12 +0000 [thread overview] Message-ID: <bug-100855-4-YpIh3YWFUv@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100855-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100855 Dominique d'Humieres <dominiq at lps dot ens.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|WAITING |RESOLVED --- Comment #9 from Dominique d'Humieres <dominiq at lps dot ens.fr> --- I don't know if the test is coming from a real world problem. The modified test program power implicit none real :: sum, sum1, n, q integer :: i, j integer :: limit real :: start, finish sum = 0d0 sum1 = 0d0 limit = 10000 n = 2.0 q = 0.5 call CPU_TIME(start) do i=1, limit n = n*q sum1 = sum1 + (i ** (0.05 + n)) end do do i=1, limit sum = sum + (i ** 0.05) end do sum = sum1 + (limit-1)*sum call CPU_TIME(finish) print *, sum, n, sum1 print '("Time = ",f6.3," seconds.")',finish-start end program power yields 150945680. 0.00000000 15095.7852 Time = 0.000 seconds.
next prev parent reply other threads:[~2021-06-05 11:59 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-01 13:01 [Bug fortran/100855] New: " nadavhalahmi560 at gmail dot com 2021-06-01 16:19 ` [Bug fortran/100855] " kargl at gcc dot gnu.org 2021-06-01 17:20 ` anlauf at gcc dot gnu.org 2021-06-02 7:52 ` rguenth at gcc dot gnu.org 2021-06-02 9:37 ` nadavhalahmi560 at gmail dot com 2021-06-02 9:38 ` nadavhalahmi560 at gmail dot com 2021-06-02 16:34 ` dominiq at lps dot ens.fr 2021-06-03 8:21 ` nadavhalahmi560 at gmail dot com 2021-06-03 14:24 ` dominiq at lps dot ens.fr 2021-06-05 11:59 ` dominiq at lps dot ens.fr [this message] 2021-06-06 8:52 ` nadavhalahmi560 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=bug-100855-4-YpIh3YWFUv@http.gcc.gnu.org/bugzilla/ \ --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: 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).