This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: [Patch, libgfortran] FIX PR26509 Catch EOR on DIRECT access write
- From: "François-Xavier Coudert" <fxcoudert at gmail dot com>
- To: "Jerry DeLisle" <jvdelisle at verizon dot net>
- Cc: "Fortran List" <fortran at gcc dot gnu dot org>
- Date: Mon, 13 Mar 2006 09:43:19 +0100
- Subject: Re: [Patch, libgfortran] FIX PR26509 Catch EOR on DIRECT access write
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=QoJE0bhsEFc48fz6bqdzRjByGeizfjhdDxwV0JmXDBu5P/skTlmAI/CiJ+OM69kOWCp3ZpCn984xF6p10yU3ZY7d1Fojn7F8SKgxR7gT0Un69mmuntjPd7xnsLw5YVjK7FOVYA4ASC2T1gcKyuU0LgfN5pnUznsfdcqcL0yCb8I=
- References: <4414F60E.9090100@verizon.net> <44152BA4.6080500@verizon.net>
> write(unit=10,rec=1) 1d0 ! { dg-error "*Write exceeds length of DIRECT
> access record*" }
Hum... I don't think we can test for runtime errors. Maybe with
dg-output, but how do you mark that the test is expected to fail (and
not XFAIL it)?
On the other hand, you could simply use an error label or an iostat,
and check that it's non-zero after the write.
FX