From: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
To: blomqvist.janne@gmail.com
Cc: hp@axis.com, fortran@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: Committed: fd_truncate test-cases updated for recent libgfortran changes
Date: Thu, 05 May 2011 18:48:00 -0000 [thread overview]
Message-ID: <201105051838.p45IcpBM005884@ignucius.se.axis.com> (raw)
In-Reply-To: <BANLkTimhqKCcPGk+SZ=hj09tB1bmuzPxgw@mail.gmail.com> (message from Janne Blomqvist on Thu, 5 May 2011 19:36:47 +0300)
> Date: Thu, 5 May 2011 19:36:47 +0300
> From: Janne Blomqvist <blomqvist.janne@gmail.com>
> On Thu, May 5, 2011 at 00:52, Hans-Peter Nilsson
> <hans-peter.nilsson@axis.com> wrote:
> > This time, it happened in 173155:173168.
> >
> > Usually, there's also a brief question whether all changes were
> > intended, or perhaps that some of the regressing tests (here:
> > gfortran.dg/fmt_cache_1.f and gfortran.dg/ftell_3.f90) were not
> > really supposed to have raw_truncate called. Â So, should they?
>
> I don't know; If you cared to bisect, that would help.
There's nothing to bisect, there was just one big libgfortran
change in the range I mentioned, one you should already know
about. :)
> These issues
> tend to fly under the radar as most developers have ftruncate()
> present. Maybe some script hack running the testsuite under strace()
> and cross-checking for the presence of "target fd_truncate" might do
> on "normal" targets, but I haven't looked into it.
I wouldn't say that this needs any priority, but I like the idea
of a portion of an I/O-library checking regression in the number
of syscalls using strace (pruning the startup and finish for
obvious reasons).
> > Two of the test-cases, gfortran.dg/endfile_3.f90 and
> > gfortran.dg/endfile_4.f90 actually pass, which seems wrong, as
> > raw_truncate after emitting the error message returns an error
> > indication (so, the test-program should abort or return an error
> > AFAICT). Â Perhaps due to lack of error handling in the
> > call-chain to raw_truncate?
Ignore that, I missed the dg-shouldfail:s. Or at most note that
dg-shouldfail should be improved to actually look for its
argument in order to distinguish between the expected failure
message and others. Right now it "accepts" any failure.
brgds, H-P
prev parent reply other threads:[~2011-05-05 18:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 22:10 Hans-Peter Nilsson
2011-05-05 16:44 ` Janne Blomqvist
2011-05-05 18:08 ` Mike Stump
2011-05-05 18:48 ` Hans-Peter Nilsson [this message]
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=201105051838.p45IcpBM005884@ignucius.se.axis.com \
--to=hans-peter.nilsson@axis.com \
--cc=blomqvist.janne@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=hp@axis.com \
/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).