public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ryan.maclellan at ua dot edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/52087] New: program does not follow logical rules Date: Thu, 02 Feb 2012 00:17:00 -0000 [thread overview] Message-ID: <bug-52087-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52087 Bug #: 52087 Summary: program does not follow logical rules Classification: Unclassified Product: gcc Version: 4.4.3 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libfortran AssignedTo: unassigned@gcc.gnu.org ReportedBy: ryan.maclellan@ua.edu Created attachment 26549 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26549 minimal source code to reproduce bug (5 lines) The following program tests if the input logical variable is a valid logical variable. It only behaves as expected if the two logical tests are separately in () although from the order of operations I would expect it to work as is. Incidentally, if I make nt_save .false. or interchange the true and false in the if statement it does work without the (). does not write: program main logical*4 nt_save/.true./ if ( nt_save.eqv..true. .or. nt_save.eqv..false. ) then write(*,*) nt_save endif end does write with if ( (nt_save.eqv..true.) .or. (nt_save.eqv..false.) ) then
next reply other threads:[~2012-02-02 0:17 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-02 0:17 ryan.maclellan at ua dot edu [this message] 2012-02-02 0:46 ` [Bug libfortran/52087] " kargl at gcc dot gnu.org 2012-02-02 0:58 ` ryan.maclellan at ua dot edu 2012-02-02 2:10 ` sgk at troutmask dot apl.washington.edu 2012-02-02 2:32 ` ryan.maclellan at ua dot edu 2012-02-02 8:36 ` burnus 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-52087-4@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).