public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "David dot Webb at noc dot soton dot ac dot uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/23638] Print format generates compiler segmentation fault
Date: Tue, 30 Aug 2005 16:19:00 -0000 [thread overview]
Message-ID: <20050830160111.11314.qmail@sourceware.org> (raw)
In-Reply-To: <20050830150741.23638.David.Webb@soc.soton.ac.uk>
------- Additional Comments From David dot Webb at noc dot soton dot ac dot uk 2005-08-30 16:00 -------
Subject: Re: Print format generates compiler segmentation fault
On Tuesday 30 August 2005 16:25, pinskia at gcc dot gnu dot org wrote:
> ------- Additional Comments From pinskia at gcc dot gnu dot org 2005-08-30
> 15:25 ------- On the mainline, I get:
>
> In file t.f:24
>
> PRINT AOUT,1,2,3,4
> 1
> Error: Syntax error in PRINT statement at (1)
Thanks for your feedback.
Of course the report refers to the GCC current release 4.0.1 referred to in
http://www.gnu.org/software/gcc/gcc.html
I have never used the development versions - I need to use the code in my work
and so require a version without development bugs - but I assume that what
you are saying implies that the print problem will be solved in future
releases. Is this correct?
Regards,
David Webb
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23638
next prev parent reply other threads:[~2005-08-30 16:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-30 15:10 [Bug fortran/23638] New: " David dot Webb at soc dot soton dot ac dot uk
2005-08-30 15:29 ` [Bug fortran/23638] " pinskia at gcc dot gnu dot org
2005-08-30 16:19 ` David dot Webb at noc dot soton dot ac dot uk [this message]
2005-08-30 16:22 ` pinskia at gcc dot gnu dot org
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=20050830160111.11314.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).