public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Richard Guenther <rguenth@tat.physik.uni-tuebingen.de> To: toon@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: fortran/7541: DATA statement for double precision variables does not work Date: Thu, 08 Aug 2002 09:16:00 -0000 [thread overview] Message-ID: <20020808161602.11618.qmail@sources.redhat.com> (raw) The following reply was made to PR fortran/7541; it has been noted by GNATS. From: Richard Guenther <rguenth@tat.physik.uni-tuebingen.de> To: <toon@gcc.gnu.org>, <gcc-bugs@gcc.gnu.org>, <gcc-prs@gcc.gnu.org>, <nobody@gcc.gnu.org>, <gcc-gnats@gcc.gnu.org> Cc: Subject: Re: fortran/7541: DATA statement for double precision variables does not work Date: Thu, 8 Aug 2002 18:07:12 +0200 (CEST) On 8 Aug 2002 toon@gcc.gnu.org wrote: > Synopsis: DATA statement for double precision variables does not work > > Responsible-Changed-From-To: unassigned->toon > Responsible-Changed-By: toon > Responsible-Changed-When: Thu Aug 8 07:35:08 2002 > Responsible-Changed-Why: > Fortran Maintainer > State-Changed-From-To: open->closed > State-Changed-By: toon > State-Changed-When: Thu Aug 8 07:35:08 2002 > State-Changed-Why: > Not legal code, but is compilable as an extension to > Fortran 77 Oh well - please make this a feature request to support this in g77 then. Its sad we cant compile the NAG library. Richard. -- Richard Guenther <richard.guenther@uni-tuebingen.de> WWW: http://www.tat.physik.uni-tuebingen.de/~rguenth/ The GLAME Project: http://www.glame.de/
next reply other threads:[~2002-08-08 16:16 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-08-08 9:16 Richard Guenther [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-08-08 7:37 toon 2002-08-08 5:06 rguenth
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=20020808161602.11618.qmail@sources.redhat.com \ --to=rguenth@tat.physik.uni-tuebingen.de \ --cc=gcc-prs@gcc.gnu.org \ --cc=toon@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).