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: Sat, 16 Mar 2013 18:46:00 -0000	[thread overview]
Message-ID: <bug-56637-4-vskHsBjxli@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 #3 from Fred Krogh <fkrogh#gcc at mathalacarte dot com> 2013-03-16 18:46:06 UTC ---
First some confusion.  If I single step over the first statement it works
properly. Once past that confusion, deleting both -floop-block and
-floop-strip-mine from the make file it still fails.

Although the test case I'm running is small, the actual code is quite large.

After realizing the problem with single stepping over the statement causing it
to work, I just tried that with the extra statement in front, and that actually
fails if I set the breakpoint after k is defined. So that part of my original
post should be ignored.

When I tried a small test case before, I had not used the same flags as caused
failure.  I just tried such a case, and it worked, so no luck in generating a
small test case.


  parent reply	other threads:[~2013-03-16 18:46 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 [this message]
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
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-vskHsBjxli@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).