This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: chmod_1, chmod_2, chmod_3 and lrshift_1
- From: Steve Kargl <sgk at troutmask dot apl dot washington dot edu>
- To: Jack Howarth <howarth at bromo dot msbb dot uc dot edu>
- Cc: fortran at gcc dot gnu dot org
- Date: Mon, 31 Jul 2006 07:38:59 -0700
- Subject: Re: chmod_1, chmod_2, chmod_3 and lrshift_1
- References: <20060731134043.25EA4110009@bromo.msbb.uc.edu>
On Mon, Jul 31, 2006 at 09:40:43AM -0400, Jack Howarth wrote:
> I noticed that x86_64-suse-linux-gnu appears to be suffering from the
> compilation errors on the lrshift_1 test as well as MacOS X...
>
This one is fixed. A file was ommitted from the check-in.
> ...although no other architectures seem to have the problems I see with
> chmod_1, chmod_2, chmod_3, stat_1 and stat_2. As I mentioned before
> about those tests, there doesn't appear to be a specific error message
> logged in the gfortran testsuite log.
I don't see these errors of FreeBSD.
> I am wondering if it is possible to add an additional flag to the
> dg-options of those tests that would cause a complete log of the
> execution to be saved? We need that since whatever is happening doesn't
> reproduce when the test are manually compiled and run.
You could try adding { dg-options "-v" }, but I don't
know if dejagnu can handle the output.
--
Steve