public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl dot tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/45131] [4.6 regression] New Fortran test failures
Date: Thu, 29 Jul 2010 15:48:00 -0000 [thread overview]
Message-ID: <20100729154757.2593.qmail@sourceware.org> (raw)
In-Reply-To: <bug-45131-682@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from hjl dot tools at gmail dot com 2010-07-29 15:47 -------
(In reply to comment #4)
> HJ, as it works on most systems, can you do some debugging?
Trunk was broken since yesterday and was fixed a while ago.
> a) Does the system has HAVE_TTYNAME defined for libgfortran/ ?
Yes.
> b) If it fails in the library, how? Otherwise: Which of the asserts fails in
> the test case? Can you replace for the failing line the "call abort()" by
> "print *, <variable name>"
>
[hjl@gnu-1 gfortran]$ cat inquire_3.f90
! pr14836
OPEN(UNIT=9, ACCESS='DIRECT', RECL=80, FORM='UNFORMATTED')
INQUIRE(UNIT=9,NEXTREC=NREC)
WRITE(UNIT=9,REC=5) 1
INQUIRE(UNIT=9,NEXTREC=NREC)
PRINT*,NREC
IF (NREC.NE.6) CALL ABORT
READ(UNIT=9,REC=1) MVI
INQUIRE(UNIT=9,NEXTREC=NREC)
PRINT*,NREC
IF (NREC.NE.2) CALL ABORT
CLOSE(UNIT=9,STATUS='DELETE')
END
[hjl@gnu-1 gfortran]$
/export/gnu/import/svn/gcc-test/bld/gcc/testsuite/gfortran/../../gfortran
-B/export/gnu/import/svn/gcc-test/bld/gcc/testsuite/gfortran/../../
inquire_3.f90 -w -O0
-B/export/gnu/import/svn/gcc-test/bld/i686-linux/./libgfortran/.libs
-L/export/gnu/import/svn/gcc-test/bld/i686-linux/./libgfortran/.libs
-L/export/gnu/import/svn/gcc-test/bld/i686-linux/./libgfortran/.libs
-L/export/gnu/import/svn/gcc-test/bld/i686-linux/./libiberty -lm -static
[hjl@gnu-1 gfortran]$ ./a.out
1
Aborted
[hjl@gnu-1 gfortran]$
--
hjl dot tools at gmail dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[4.6 regression] New test |[4.6 regression] New Fortran
|failures configured with -- |test failures
|with-cpu=atom |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45131
next prev parent reply other threads:[~2010-07-29 15:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-29 14:11 [Bug middle-end/45131] New: [4.6 regression] New test failures configured with --with-cpu=atom hjl dot tools at gmail dot com
2010-07-29 14:13 ` [Bug middle-end/45131] " hjl dot tools at gmail dot com
2010-07-29 14:16 ` hjl dot tools at gmail dot com
2010-07-29 14:19 ` hjl dot tools at gmail dot com
2010-07-29 14:56 ` burnus at gcc dot gnu dot org
2010-07-29 15:48 ` hjl dot tools at gmail dot com [this message]
2010-07-30 1:50 ` [Bug fortran/45131] [4.6 regression] New Fortran test failures jvdelisle at gcc dot gnu dot org
2010-07-30 9:32 ` rguenth at gcc dot gnu dot org
2010-07-30 14:06 ` jvdelisle at gcc dot gnu dot org
2010-07-30 15:12 ` burnus at gcc dot gnu dot org
2010-07-31 16:29 ` jvdelisle at gcc dot gnu dot org
2010-07-31 17:05 ` jvdelisle at gcc dot gnu dot org
2010-08-01 17:28 ` jvdelisle at gcc dot gnu dot org
2010-08-01 19:38 ` burnus at gcc dot gnu dot org
2010-08-02 13:19 ` jvdelisle 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=20100729154757.2593.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).