public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/67174] [6 regression] gfortran.dg/do_iterator.f90 FAILs
Date: Mon, 31 Aug 2015 11:36:00 -0000 [thread overview]
Message-ID: <bug-67174-4-Rh8kwh03x2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67174-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67174
Rainer Orth <ro at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |INVALID
--- Comment #3 from Rainer Orth <ro at gcc dot gnu.org> ---
(In reply to Paul Thomas from comment #1)
> If you run the testcase outside of the testsuite does the error appear but
> without the offending line? I have been plagued by such a problem with an
> F2008 patch that I have prepared.
It does indeed. It occured to me that this might be the same problem which
causes
FAIL: gcc.dg/unroll-2.c (test for warnings, line 24)
on Solaris 11 only (S10 and S12 are both fine). This seems to be a kernel bug
causing truncation of pty output.
I might xfail both testcases to avoid the noise if this can be confirmed.
Rainer
prev parent reply other threads:[~2015-08-31 11:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-10 13:48 [Bug fortran/67174] New: " ro at gcc dot gnu.org
2015-08-10 13:49 ` [Bug fortran/67174] " ro at gcc dot gnu.org
2015-08-29 16:16 ` pault at gcc dot gnu.org
2015-08-30 13:30 ` dominiq at lps dot ens.fr
2015-08-31 11:36 ` ro at gcc dot gnu.org [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=bug-67174-4-Rh8kwh03x2@http.gcc.gnu.org/bugzilla/ \
--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).