From: Toon Moene <toon@moene.indiv.nluug.nl>
To: "Steven G. Kargl" <kargl@troutmask.apl.washington.edu>
Cc: Bud Davis <bdavis9659@comcast.net>, gcc <gcc@gcc.gnu.org>
Subject: Re: g77 compiles illegal code in testsuite?
Date: Fri, 23 May 2003 22:57:00 -0000 [thread overview]
Message-ID: <3ECE9BFD.5000008@moene.indiv.nluug.nl> (raw)
In-Reply-To: <200305231507.h4NF7BW7001016@troutmask.apl.washington.edu>
Steven G. Kargl wrote:
> It's Toon's call, but I think g77 should issue an error and
> abort. The g77 info contains a -fno-ugly-args option. I
> would think you should need -fugly-args to compile the code
> in question.
I think I agree with that stance.
>>Of course, IMHO, g95 should be backwards compatable with g77 :)
> This may not happen, because Fortran 95 has deleted a few
> features from Fortran 77.
Ah yes, the language has. However, as compiler writers we could decide
to include the complete language g77 compiles into the language g95
compiles.
This would have the obvious benefit of making g77 superfluous and
reducing our maintenance burden.
--
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
GNU Fortran 95: http://gcc-g95.sourceforge.net/ (under construction)
next prev parent reply other threads:[~2003-05-23 22:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-23 12:57 Bud Davis
2003-05-23 14:23 ` Paul Brook
2003-05-23 15:15 ` Steven G. Kargl
2003-05-23 15:36 ` Bud Davis
2003-05-23 22:57 ` Toon Moene [this message]
2003-05-23 23:40 ` Steven Bosscher
-- strict thread matches above, loose matches on Subject: below --
2003-05-23 3:33 Steven G. Kargl
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=3ECE9BFD.5000008@moene.indiv.nluug.nl \
--to=toon@moene.indiv.nluug.nl \
--cc=bdavis9659@comcast.net \
--cc=gcc@gcc.gnu.org \
--cc=kargl@troutmask.apl.washington.edu \
/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).