--- Comment #19 from fxcoudert at gcc dot gnu dot org 2006-05-26 08:31
---
(In reply to comment #18)
This patch is beyond my current understanding, so someone else needs to look
at
it.
I think our best chance here is to find the exact patch that broke it. You said
it's between
--- Comment #20 from dje at gcc dot gnu dot org 2006-05-26 14:07 ---
The patch you reference enables section anchors by default. Neither AIX nor
PPC Linux show new Gfortran testsuite failures from the use of section anchors.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27683
--- Comment #21 from dir at lanl dot gov 2006-05-26 17:45 ---
It is rev 113395 that is causing the problem. I backed out that change and
built today's version of gfortran - it now correctly runs one of the tests that
has been failing -
[dranta:~/tests/gfortran-D] dir% gfortran -O1 -o
--- Comment #10 from dir at lanl dot gov 2006-05-25 13:36 ---
I restored and rebuilt the 20060508 version that I had archived and I still get
the error -
[dranta:~/tests/gfortran-D] dir% gfortran -O1 -o write_logical
write_logical.f90
[dranta:~/tests/gfortran-D] dir% write_logical
At
--- Comment #11 from howarth at nitro dot med dot uc dot edu 2006-05-25
14:04 ---
Dale,
I am confused. Are you saying the breakage in gcc trunk goes
as far back as 20060508? I was going to try a few builds here on
my G5 to see if I can narrow down the svn revision numbers involved.
--- Comment #12 from dir at lanl dot gov 2006-05-25 14:35 ---
I rebuild version 20060508 from the full source tree that I had saved and I
find the problem - I am beginning to wonder if the update to CCTOOLS or the
system is causing the problem - except for the fact that I can build the
--- Comment #13 from jvdelisle at gcc dot gnu dot org 2006-05-25 14:44
---
Maybe go back farther than the email I just posted to gfortran list suggests.
I am suspicious that this is not a gfortran problem, but then 4.1 is working.
Take a shot at an April 1 version maybe. You can
--- Comment #14 from dir at lanl dot gov 2006-05-25 14:47 ---
The version from the wiki also fails -
[dranta:~/tests/gfortran-D] dir% gfortran -O1 -o write_logical
write_logical.f90
[dranta:~/tests/gfortran-D] dir% write_logical
At line 9 of file write_logical.f90
Fortran runtime
--- Comment #15 from dir at lanl dot gov 2006-05-25 14:54 ---
At last one that works (I knew that I did the testsuite on this one) - version
20060405 -
[dranta:~/tests/gfortran-D] dir% gfortran -O1 -o write_logical
write_logical.f90
[dranta:~/tests/gfortran-D] dir% write_logical
--- Comment #16 from dir at lanl dot gov 2006-05-25 16:33 ---
Works at rev 112998 just before the updates for bug 27138 on April 17 -
[dranta:~/tests/gfortran-D] dir% gfortran -O1 -o write_logical
write_logical.f90
[dranta:~/tests/gfortran-D] dir% write_logical
--- Comment #17 from dir at lanl dot gov 2006-05-25 20:53 ---
It runs after (bug fix 20257) rev 113373 and fails after (bug fix 27360) rev
113396. I think that narrows it down to one of two updates - if the problem was
caused by changes to gfortran.
--
--- Comment #18 from jvdelisle at gcc dot gnu dot org 2006-05-26 00:08
---
All of the IO patches for both revs, before and after the failures, exist in
4.1 and 4.2. 4.1 is not failing, so this leads me to believe this is not a
libgfortran failure.
There is an alignment patch that
--- Comment #6 from fxcoudert at gcc dot gnu dot org 2006-05-24 06:14
---
Reduced testcase (fails at -O1 and higher):
character*1 b
b = ''
write (*, '()')
end
is compiled into (-gfump-original-tree):
MAIN__ ()
{
char b[1:1];
_gfortran_set_std (70,
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2006-05-24 13:48
---
Look in Changelog and you will see the most recent two in trunk have not gone
to 4.1 yet. The namelist patch for expanded reads does touch io.h
The other was a simple problem. I changed a return; to return
--- Comment #8 from dir at lanl dot gov 2006-05-24 18:27 ---
Hi Jerry,
I tried rev 113947 and rev 113923 that I think are just before your
patches and gfortran still failed. I did a svn update -r 113923 gcc to create
the old version. I hope that is the correct way to do it.
--- Comment #9 from jvdelisle at gcc dot gnu dot org 2006-05-25 00:40
---
Dale,
I believe this is the correct use of update to get back to previous versions if
gcc is your main trunk directory and you were one directory above when you
invoked the command. You may want to check in
--- Comment #5 from dir at lanl dot gov 2006-05-23 19:16 ---
Has anybody else with a powerPC Macintosh tried the testsuite recently ?
I down loaded and rebuild 4.1.1 and 4.2.0 today. 4.1.1 is Ok. 4.2.0 has the
same errors.
The test problem in comment #3 works with -g, but when
--- Comment #2 from dir at lanl dot gov 2006-05-22 14:41 ---
Hi Paul,
I down loaded a completely new tree this morning and did a new build with
about the same results -
Test Run By dir on Mon May 22 07:08:14 2006
Native configuration is powerpc-apple-darwin8.6.0
--- Comment #3 from dir at lanl dot gov 2006-05-22 14:58 ---
I grabbed one of the tests that failed and tried it with today's 4.2.0 version
and version 4.1.1 and it failed with the new and passed with the old -
[dranta:~/tests/gfortran-D] dir% gfortran -O1 -o write_logical
--- Comment #4 from dir at lanl dot gov 2006-05-22 20:51 ---
There is no problem on LINUX or the Intel Macintosh version - only having
trouble with the powerPC version.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27683
--- Comment #1 from pault at gcc dot gnu dot org 2006-05-21 13:49 ---
Dale,
This looks like a library problem. Jerry committed a change that might have
required a completely clean tree to build.
I had no trouble with the trunk of two hours ago on FC5/Athlon.
Paul
--
21 matches
Mail list logo
