public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: aurag@cae.com
To: gcc-gnats@gcc.gnu.org
Subject: fortran/6491: Logical operations error on logicals when using -fugly-logint
Date: Sat, 27 Apr 2002 14:06:00 -0000	[thread overview]
Message-ID: <20020427210538.14256.qmail@sources.redhat.com> (raw)


>Number:         6491
>Category:       fortran
>Synopsis:       Logical operations error on logicals when using -fugly-logint
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Apr 27 14:06:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Hassan Aurag
>Release:        gcc version 2.95.1 19990816 (release)/GNU Fortran 0.5.25 19990816 (release)
>Organization:
>Environment:
Linux ibdu 2.2.12-20 #1 Fri Sep 29 07:29:24 EDT 2000 i686 unknown(RedHat 6.1)
>Description:
Doing parallel byte operations with and's, or's fails to run correctly when using --fugly-logint.

The file below is good example of how a.and.b works differently from and(a,b)

Please compile example with g77 -fugly-logint
>How-To-Repeat:
Just compile file with -fugly-logint and run to see difference between 2 outputs.
>Fix:
I have no idea, except that .and. should behave as and(.,.) in my opinion. But I am no expert.
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="ands1.f"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="ands1.f"

ICAgICAgICBwcm9ncmFtIHBhcmFsbGVsDQogICAgICAgIGxvZ2ljYWwqNCBsNCwgbGw0DQogICAg
ICAgIGxvZ2ljYWwqMSBsMSg0KSwgbGwxKDQpDQogICAgICAgIGxvZ2ljYWwqNCB0cnVlIC9YJzAx
MDEwMTAxJy8NCiAgICAgICAgaW50ZWdlciBpDQogICAgICAgIGVxdWl2YWxlbmNlKGwxLCBsNCks
IChsbDEsIGxsNCkNCkMgICAgIFNldHRpbmcgZmlyc3QgYW5kIHRoaXJkIGVsZW1lbnRzIG9mIGxv
Z2ljYWwqNCB0byB0cnVlDQogICAgICAgIGxsMSgxKSA9IC50cnVlLg0KICAgICAgICBsbDEoMykg
PSAudHJ1ZS4NCkMgICAgIFVzaW5nIG5vcm1hbCAuYW5kLiBvcGVyYXRvcg0KICAgICAgICBsNCA9
IGxsNCAuYW5kLiB0cnVlDQoNCiAgICAgICAgZG8gaSA9MSwgNA0KICAgICAgICAgICAgICAgIHBy
aW50ICosIGwxKGkpDQogICAgICAgIGVuZGRvDQpDICAgICBOb3cgdXNpbmcgYW5kKC4sLikgb3Bl
cmF0b3IuIFRoZSBzYW1lIGFwcGxpZXMgZm9yIE9SL1hPUiAuLi4NCglsNCA9IGFuZChsbDQsIHRy
dWUpDQogICAgICAgIGRvIGkgPTEsIDQNCiAgICAgICAgICAgICAgICBwcmludCAqLCBsMShpKQ0K
ICAgICAgICBlbmRkbw0KDQogICAgICAgIGVuZA0KICAgICAgIA0KDQogICAgICAgIA0K


             reply	other threads:[~2002-04-27 21:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-27 14:06 aurag [this message]
2002-05-09  2:17 toon

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=20020427210538.14256.qmail@sources.redhat.com \
    --to=aurag@cae.com \
    --cc=gcc-gnats@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).