public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bdavis9659 at comcast dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/21931] problem with fugly-logint flag and evaluating if statements
Date: Sat, 25 Jun 2005 13:58:00 -0000	[thread overview]
Message-ID: <20050625135848.18526.qmail@sourceware.org> (raw)
In-Reply-To: <20050606154812.21931.mark_l_hansen@yahoo.com>


------- Additional Comments From bdavis9659 at comcast dot net  2005-06-25 13:58 -------

here are some things i have found while researching this:


First, this patch:
2002-05-09  Hassan Aurag  <aurag@cae.com>

        * expr.c (ffeexpr_reduced_ugly2log_): Allow logicals-as-integers
        under -fugly-logint as arguments of .and., .or., .xor.

which was then reverted after discussion about what -fugly-logint is supposed to do:

2003-11-24  Toon Moene  <toon@moene.indiv.nluug.nl>

        PR fortran/12633
        * expr.c (ffeexpr_reduced_ugly2log_): Revert
        change allowing logical .and. logical to be
        integer in expressions when -fugly-logint.

And then another patch which was supposed to "do the right thing":

2004-01-13  Ian Lance Taylor  <ian@wasabisystems.com>

        PR fortran/6491
        * expr.c (ffeexpr_reduce_): When handling AND, OR, and XOR, and
        when using -fugly-logint, if both operands are logical, convert
        the result back to logical.
        (ffeexpr_reduced_ugly2log_): Add bothlogical parameter.  Change
        all callers.  Convert logical operands to integer.





-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bbsnider at link dot com


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


  parent reply	other threads:[~2005-06-25 13:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-06 15:48 [Bug fortran/21931] New: " mark_l_hansen at yahoo dot com
2005-06-06 15:51 ` [Bug fortran/21931] " mark_l_hansen at yahoo dot com
2005-06-10 14:53 ` bdavis9659 at comcast dot net
2005-06-18 18:48 ` fxcoudert at gcc dot gnu dot org
2005-06-19 18:39 ` mark_l_hansen at yahoo dot com
2005-06-25 13:58 ` bdavis9659 at comcast dot net [this message]
2005-06-25 14:06 ` bdavis9659 at comcast dot net
2005-06-29  2:08 ` mark_l_hansen at yahoo dot com
2005-09-09 14:36 ` bdavis9659 at comcast dot net
2005-09-09 14:38 ` bdavis9659 at comcast dot net

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=20050625135848.18526.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).