https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116701

            Bug ID: 116701
           Summary: [15 Regression] gfortran.dg/write_check3.f90 suddenly
                    fails for non-fd_truncate targets
           Product: gcc
           Version: 15.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: hp at gcc dot gnu.org
  Target Milestone: ---
            Target: cris-elf

I investigated my autotester signalling a failure appearing between (good)
r15-3525-gbb8dd0980b39cf and (bad) r15-3528-g6749c69ae143ed, with execution
starting to fail for gfortran.dg/write_check3.f90 as follows:

Running
/netapp/hp3_storage/hp/autotest/hpautotest-gcc1/gcc/gcc/testsuite/gfortran.dg/dg.exp
...
(...other failing tests, but that are not regressions, pruned...)
FAIL: gfortran.dg/write_check3.f90   -O0  execution test
FAIL: gfortran.dg/write_check3.f90   -O1  execution test
FAIL: gfortran.dg/write_check3.f90   -O2  execution test
FAIL: gfortran.dg/write_check3.f90   -O3 -fomit-frame-pointer -funroll-loops
-fpeel-loops -ftracer -finline-functions  execution test
FAIL: gfortran.dg/write_check3.f90   -O3 -g  execution test
FAIL: gfortran.dg/write_check3.f90   -Os  execution test

In the gfortran.log:
PASS: gfortran.dg/write_check3.f90   -O0  (test for excess errors)
spawn cris-elf-run ./write_check3.exe^M
Fortran runtime error: required ftruncate or chsize support not present^M
^M
Error termination. Backtrace:^M
^M
Could not print backtrace: executable file is unexpected ELF class^M
FAIL: gfortran.dg/write_check3.f90   -O0  execution test

I was happy seeing that this was "obviosly" r15-3526 and that I had to change
the first line of write_check3.f90 as "! { dg-do run { target fd_truncate } }"
but doing due diligence I noticed something weird... I can't repeat the
failure!
No matter what I do, this only appears in my autotester.  (Trying to replicate
the environment, checking a native build for valgrind-detectable
errors...nothing - at least not yet.)  I'll assume PEBKAC, and hope staring at
simulator traces will help, but I need a tracker number.  I'll set the
component to target and assign myself so no-one feels compelled to take action.

Reply via email to