This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: [RFA:] fix failing gfortran.dg/inquire_10.f90 for newlib targets
- From: Janne Blomqvist <blomqvist dot janne at gmail dot com>
- To: Hans-Peter Nilsson <hans-peter dot nilsson at axis dot com>
- Cc: gcc-patches at gcc dot gnu dot org, fortran at gcc dot gnu dot org
- Date: Sun, 20 Jan 2013 21:14:11 +0200
- Subject: Re: [RFA:] fix failing gfortran.dg/inquire_10.f90 for newlib targets
- References: <201301200029.r0K0TZbK012121@ignucius.se.axis.com>
On Sun, Jan 20, 2013 at 2:29 AM, Hans-Peter Nilsson
<hans-peter.nilsson@axis.com> wrote:
> Ever since it was changed to a "run" test (from the default
> "compile", i.e. just producing assembly code), the test
> gfortran.dg/inquire_10.f90 has failed for newlib targets while
> linking, because (besides cygwin and some linux support), newlib
> doesn't have getcwd:
>
> /tmp/ccNhxU2l.o: In function `MAIN__':
> inquire_10.f90:(.text+0x22): undefined reference to `_gfortran_getcwd_i4_sub'
> collect2: error: ld returned 1 exit status
>
> Digging into the history of the test-case, it was clearly
> intended as a run-target, with nothing interesting compile-wise,
> so I thought best to simply disable it for newlib targets, using
> the available effective-target newlib. Just about obvious, but
> not. Tested x86_64-unknown-linux-gnu to check that I didn't
> goof (tests still passes), verified that the test is now
> disabled for cris-elf.
>
> Ok to commit?
Ok.
Alternatively, I don't think the getcwd() stuff in that testcase does
anything particularly useful related to the inquire functionality, so
one might instead remove lines 5, 10, and 11. Consider such a patch
pre-approved if you'd rather prefer that.
--
Janne Blomqvist