On Sat, Oct 23, 2021 at 5:34 AM H.J. Lu <hjl.to...@gmail.com> wrote:
>
> On Sat, Oct 23, 2021 at 5:31 AM H.J. Lu <hjl.to...@gmail.com> wrote:
> >
> > On Fri, Oct 22, 2021 at 11:20 PM Tobias Burnus <tob...@codesourcery.com> 
> > wrote:
> > >
> > > Hi,
> > >
> > > for some reasons, I cannot reproduce this. I checked with that I am in
> > > sync with master – and I also tried -m32 and -march=cascadelake, running
> > > both manually and via DejaGNU but I it passes here.
> > >
> > > Can someone who sees it show the excess error? Or was that a spurious
> > > issue which is now  gone?
> >
> > spawn -ignore SIGHUP
> > /export/gnu/import/git/gcc-test-master-intel64-native/bld/gcc/testsuite/gfortran2/../../gfortran
> > -B/export/gnu/import/git/gcc-test-master-intel64-native/bld/gcc/testsuite/gfortran2/../../
> > -B/export/gnu/import/git/gcc-test-master-intel64-native/bld/x86_64-pc-linux-gnu/./libgfortran/
> > /export/gnu/import/git/gcc-test-master-intel64-native/src-master/gcc/testsuite/gfortran.dg/bind-c-intent-out-2.f90
> > -fdiagnostics-plain-output -fdiagnostics-plain-output -O0
> > -pedantic-errors -fsanitize=undefined -fcheck=all
> > -B/export/gnu/import/git/gcc-test-master-intel64-native/bld/x86_64-pc-linux-gnu/./libgfortran/.libs
> > -L/export/gnu/import/git/gcc-test-master-intel64-native/bld/x86_64-pc-linux-gnu/./libgfortran/.libs
> > -L/export/gnu/import/git/gcc-test-master-intel64-native/bld/x86_64-pc-linux-gnu/./libgfortran/.libs
> > -L/export/gnu/import/git/gcc-test-master-intel64-native/bld/x86_64-pc-linux-gnu/./libatomic/.libs
> > -B/export/gnu/import/git/gcc-test-master-intel64-native/bld/x86_64-pc-linux-gnu/./libquadmath/.libs
> > -L/export/gnu/import/git/gcc-test-master-intel64-native/bld/x86_64-pc-linux-gnu/./libquadmath/.libs
> > -L/export/gnu/import/git/gcc-test-master-intel64-native/bld/x86_64-pc-linux-gnu/./libquadmath/.libs
> > -lm -o ./bind-c-intent-out-2.exe
> > /usr/local/bin/ld: cannot find -lubsan: No such file or directory
> >
> > Shouldn't the test be placed under gfortran.dg/ubsan?
>
> I am checking it as an obvious fix.

>From d891ab1bc87bc5d855f6ee18337e517a2a90d759 Mon Sep 17 00:00:00 2001
From: "H.J. Lu" <hjl.to...@gmail.com>
Date: Sat, 23 Oct 2021 05:40:09 -0700
Subject: [PATCH] Move bind-c-intent-out-2.f90 to gfortran.dg/ubsan

Move bind-c-intent-out-2.f90 to gfortran.dg/ubsan for -fsanitize=undefined.

PR fortran/9262
* gfortran.dg/bind-c-intent-out-2.f90: Moved to ...
* gfortran.dg/ubsan/bind-c-intent-out-2.f90
---
 gcc/testsuite/gfortran.dg/{ => ubsan}/bind-c-intent-out-2.f90 | 0
 1 file changed, 0 insertions(+), 0 deletions(-)
 rename gcc/testsuite/gfortran.dg/{ => ubsan}/bind-c-intent-out-2.f90 (100%)

diff --git a/gcc/testsuite/gfortran.dg/bind-c-intent-out-2.f90
b/gcc/testsuite/gfortran.dg/ubsan/bind-c-intent-out-2.f90
similarity index 100%
rename from gcc/testsuite/gfortran.dg/bind-c-intent-out-2.f90
rename to gcc/testsuite/gfortran.dg/ubsan/bind-c-intent-out-2.f90

-- 
H.J.

Reply via email to