This is the mail archive of the fortran@gcc.gnu.org mailing list for the GNU Fortran project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: some problems with gcc/testsuite/gfortran.dg/ tests in 4.3-20061111 with OSX 10.3


> For 10.4 on powerpc, the only failures I got was the large kind failures
> which are known issues.

I don't know if the regression tests have a 'time out' failure, but if there is no
such failure (or need to manually interrupt the test if it does not exist) on
post Tue Oct 31 06:03:24 2006 UTC test suite, then I understand the problem
I reported does not show up in 10.4/ppc. From
http://gcc.gnu.org/ml/fortran/2006-11/msg00410.html
and
http://gcc.gnu.org/ml/fortran/2006-11/msg00460.html
it seems unlikely that the problem is coming from the front-end (unless
different labeling of the variables is meaningful in the context).

I am not sure to have been descrptive enough when I used "hang" and not
"infinite loop". I would have used the later if running the test have eaten
all the CPU. This is not the case, if I time the executable, it uses very little
user/system time whatever time I am waiting (up to a minute) as if something
was waiting for some noncoming event.

So I can see only two possibilities:
(1) the test case reveal a bug in 10.3, certainly a won't fix,
(2) or I have something wrong in my setup, with possibilities from
my a la Fink build to an aging system having suffering a lot of experiments!

Any idea around where I should look?

TIA

Dominique


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]