public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rob1weld at aol dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/32196] New: Upgrading GNU/Linux to libc6_2.6~20070518-2 fails gfortran.dg/secnds.f
Date: Sun, 03 Jun 2007 12:30:00 -0000 [thread overview]
Message-ID: <bug-32196-13830@http.gcc.gnu.org/bugzilla/> (raw)
Please read first portion of http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32193
to see the where and how of obtaining and installing new libc6, then come back
here.
After upgrading my library I did a diff of the "make -i check" test results of
the build before I upgraded and after I upgraded. It was identical except for
this:
# diff -Naur ../gcc-4_3-build-libc6_2.3.6/summary
../gcc-4_3-build-libc6_2.6/summary
--- ../gcc-4_3-build-libc6_2.3.6/summary 2007-06-02 15:10:51.000000000 -0700
+++ ../gcc-4_3-build-libc6_2.6/summary 2007-06-03 04:40:17.000000000 -0700
@@ -119,11 +119,12 @@
FAIL: gfortran.dg/open_errors.f90 -O3 -fomit-frame-pointer -funroll-all-loops
-finline-functions execution test
FAIL: gfortran.dg/open_errors.f90 -O3 -g execution test
FAIL: gfortran.dg/open_errors.f90 -Os execution test
+FAIL: gfortran.dg/secnds.f -O3 -fomit-frame-pointer execution test
=== gfortran Summary ===
-# of expected passes 18236
-# of unexpected failures 16
+# of expected passes 18235
+# of unexpected failures 17
# of expected failures 8
# of unsupported tests 16
/opt/gcc-4_3-build/gcc/testsuite/gfortran/../../gfortran version 4.3.0
20070602 (experimental)
The "gfortran.dg/secnds.f" test did not fail prior to my upgrade.
--
Summary: Upgrading GNU/Linux to libc6_2.6~20070518-2 fails
gfortran.dg/secnds.f
Product: gcc
Version: 4.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: rob1weld at aol dot com
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32196
next reply other threads:[~2007-06-03 12:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-03 12:30 rob1weld at aol dot com [this message]
2007-06-03 13:07 ` [Bug fortran/32196] " dominiq at lps dot ens dot fr
2007-06-03 14:14 ` jvdelisle at gcc dot gnu dot org
2007-06-03 17:07 ` pinskia at gcc dot gnu dot org
2007-06-05 18:54 ` rob1weld at aol dot com
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-32196-13830@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).