public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fkrogh#gcc at mathalacarte dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/56637] Bad result on max(1,shiftr(j,1))
Date: Sun, 17 Mar 2013 16:40:00 -0000	[thread overview]
Message-ID: <bug-56637-4-G9K8Derf4f@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56637-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #13 from Fred Krogh <fkrogh#gcc at mathalacarte dot com> 2013-03-17 16:40:22 UTC ---
As perhaps you have already guessed, this is just me being confused.  After
removing a lot of stuff from the code, I inserted a print statement thus

 620     k = max(1, shiftr(l,1)) ! The increment during the sort
 621     do ! Sort constraints to make active (Shell sort)
 622       do i = k + 1, l
 623         print '("i=",i0)', i

The break point is at line 621.  The print occurs before the break point is
reached.  The print shows that all is o.k.  I was confused as I thought the
breakpoint would be hit before getting into the loop.  Interestingly the
breakpoint has the behavior I expected with "-O1" or "-O2".

I'm sorry to have bothered you folks with this, but I'm glad to know a little
about valgrind.


  parent reply	other threads:[~2013-03-17 16:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-16 17:03 [Bug fortran/56637] New: " fkrogh#gcc at mathalacarte dot com
2013-03-16 18:03 ` [Bug fortran/56637] " fkrogh#gcc at mathalacarte dot com
2013-03-16 18:16 ` dominiq at lps dot ens.fr
2013-03-16 18:46 ` fkrogh#gcc at mathalacarte dot com
2013-03-16 21:23 ` tkoenig at gcc dot gnu.org
2013-03-16 21:27 ` fkrogh#gcc at mathalacarte dot com
2013-03-16 21:37 ` dominiq at lps dot ens.fr
2013-03-16 21:45 ` fkrogh#gcc at mathalacarte dot com
2013-03-16 23:03 ` tkoenig at gcc dot gnu.org
2013-03-17  4:42 ` fkrogh#gcc at mathalacarte dot com
2013-03-17 10:47 ` tkoenig at gcc dot gnu.org
2013-03-17 15:21 ` mikael at gcc dot gnu.org
2013-03-17 15:35 ` fkrogh#gcc at mathalacarte dot com
2013-03-17 16:40 ` fkrogh#gcc at mathalacarte dot com [this message]
2013-03-17 17:05 ` tkoenig at gcc dot gnu.org

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-56637-4-G9K8Derf4f@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: 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).