public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Hassan Aurag <aurag@cae.com>
To: "'Toon Moene'" <toon@moene.indiv.nluug.nl>, Hassan Aurag <aurag@CAE.COM>
Cc: Hassan Aurag <hassan.aurag@CAE.COM>,
	gcc-help@gcc.gnu.org, Remi Simard <remis@CAE.COM>
Subject: RE: G77: bitwise .AND. ?
Date: Mon, 29 Apr 2002 13:06:00 -0000	[thread overview]
Message-ID: <8A6A2A139700D5118EB6009027B0FF3AE26EA7@caemsx02.cae.ca> (raw)

 I'll do that. It is also the same with OR and someone told me even
XOR??!!!!


-----Original Message-----
From: Toon Moene [mailto:toon@moene.indiv.nluug.nl]
Sent: Friday, April 26, 2002 4:02 PM
To: Hassan Aurag
Cc: Hassan Aurag; gcc-help@gcc.gnu.org; Remi Simard
Subject: Re: G77: bitwise .AND. ?


Hassan Aurag wrote:

> Ok the problem below is fixed by doing
> 
> and(ll4, true) instead of ll4.and.true
> 
> In my opinion, this is a bug in G77.

Yes, it could be argued that if we want to support -fugly-logint that
the code you supplied should work as-is.

Could you file a bug report using GNATS ?

Thanks in advance,

-- 
Toon Moene - mailto:toon@moene.indiv.nluug.nl - phoneto: +31 346 214290
Saturnushof 14, 3738 XG  Maartensdijk, The Netherlands
Maintainer, GNU Fortran 77: http://gcc.gnu.org/onlinedocs/g77_news.html
Join GNU Fortran 95: http://g95.sourceforge.net/ (under construction)

             reply	other threads:[~2002-04-27 20:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-29 13:06 Hassan Aurag [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-23 11:55 Hassan Aurag
2002-04-23 14:32 ` Toon Moene
2002-04-24  7:25   ` Hassan Aurag
2002-04-24 14:32     ` Toon Moene
2002-04-26 11:47       ` Hassan Aurag
2002-04-27  3:32         ` Toon Moene

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=8A6A2A139700D5118EB6009027B0FF3AE26EA7@caemsx02.cae.ca \
    --to=aurag@cae.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=hassan.aurag@CAE.COM \
    --cc=remis@CAE.COM \
    --cc=toon@moene.indiv.nluug.nl \
    /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).