public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
* [r12-4632 Regression] FAIL: gfortran.dg/bind-c-intent-out-2.f90 -Os (test for excess errors) on Linux/x86_64
@ 2021-10-23  4:43 sunil.k.pandey
  2021-10-23  6:19 ` Cannot reproduce – " Tobias Burnus
  0 siblings, 1 reply; 5+ messages in thread
From: sunil.k.pandey @ 2021-10-23  4:43 UTC (permalink / raw)
  To: gcc-patches, gcc-regression, tobias

On Linux/x86_64,

24e99e6ec1cc57f3660c00ff677c7feb16aa94d2 is the first bad commit
commit 24e99e6ec1cc57f3660c00ff677c7feb16aa94d2
Author: Tobias Burnus <tobias@codesourcery.com>
Date:   Fri Oct 22 23:23:06 2021 +0200

    Fortran: Avoid running into assert with -fcheck= + UBSAN

caused

FAIL: gfortran.dg/bind-c-intent-out-2.f90   -O0  (test for excess errors)
FAIL: gfortran.dg/bind-c-intent-out-2.f90   -O1  (test for excess errors)
FAIL: gfortran.dg/bind-c-intent-out-2.f90   -O2  (test for excess errors)
FAIL: gfortran.dg/bind-c-intent-out-2.f90   -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions  (test for excess errors)
FAIL: gfortran.dg/bind-c-intent-out-2.f90   -O3 -g  (test for excess errors)
FAIL: gfortran.dg/bind-c-intent-out-2.f90   -Os  (test for excess errors)

with GCC configured with

../../gcc/configure --prefix=/local/skpandey/gccwork/toolwork/gcc-bisect-master/master/r12-4632/usr --enable-clocale=gnu --with-system-zlib --with-demangler-in-ld --with-fpmath=sse --enable-languages=c,c++,fortran --enable-cet --without-isl --enable-libmpx x86_64-linux --disable-bootstrap

To reproduce:

$ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gfortran.dg/bind-c-intent-out-2.f90 --target_board='unix{-m32}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gfortran.dg/bind-c-intent-out-2.f90 --target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gfortran.dg/bind-c-intent-out-2.f90 --target_board='unix{-m64}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gfortran.dg/bind-c-intent-out-2.f90 --target_board='unix{-m64\ -march=cascadelake}'"

(Please do not reply to this email, for question about this report, contact me at skpgkp2 at gmail dot com)

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Cannot reproduce – Re: [r12-4632 Regression] FAIL: gfortran.dg/bind-c-intent-out-2.f90 -Os (test for excess errors) on Linux/x86_64
  2021-10-23  4:43 [r12-4632 Regression] FAIL: gfortran.dg/bind-c-intent-out-2.f90 -Os (test for excess errors) on Linux/x86_64 sunil.k.pandey
@ 2021-10-23  6:19 ` Tobias Burnus
  2021-10-23 12:31   ` H.J. Lu
  0 siblings, 1 reply; 5+ messages in thread
From: Tobias Burnus @ 2021-10-23  6:19 UTC (permalink / raw)
  To: skpgkp2, gcc-patches, gcc-regression

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?

Tobias

On 23.10.21 06:43, sunil.k.pandey wrote:
> On Linux/x86_64,
>
> 24e99e6ec1cc57f3660c00ff677c7feb16aa94d2 is the first bad commit
> commit 24e99e6ec1cc57f3660c00ff677c7feb16aa94d2
> Author: Tobias Burnus <tobias@codesourcery.com>
> Date:   Fri Oct 22 23:23:06 2021 +0200
>
>      Fortran: Avoid running into assert with -fcheck= + UBSAN
>
> caused
>
> FAIL: gfortran.dg/bind-c-intent-out-2.f90   -O0  (test for excess errors)
> FAIL: gfortran.dg/bind-c-intent-out-2.f90   -O1  (test for excess errors)
> FAIL: gfortran.dg/bind-c-intent-out-2.f90   -O2  (test for excess errors)
> FAIL: gfortran.dg/bind-c-intent-out-2.f90   -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions  (test for excess errors)
> FAIL: gfortran.dg/bind-c-intent-out-2.f90   -O3 -g  (test for excess errors)
> FAIL: gfortran.dg/bind-c-intent-out-2.f90   -Os  (test for excess errors)
>
> with GCC configured with
>
> ../../gcc/configure --prefix=/local/skpandey/gccwork/toolwork/gcc-bisect-master/master/r12-4632/usr --enable-clocale=gnu --with-system-zlib --with-demangler-in-ld --with-fpmath=sse --enable-languages=c,c++,fortran --enable-cet --without-isl --enable-libmpx x86_64-linux --disable-bootstrap
>
> To reproduce:
>
> $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gfortran.dg/bind-c-intent-out-2.f90 --target_board='unix{-m32}'"
> $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gfortran.dg/bind-c-intent-out-2.f90 --target_board='unix{-m32\ -march=cascadelake}'"
> $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gfortran.dg/bind-c-intent-out-2.f90 --target_board='unix{-m64}'"
> $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gfortran.dg/bind-c-intent-out-2.f90 --target_board='unix{-m64\ -march=cascadelake}'"
>
> (Please do not reply to this email, for question about this report, contact me at skpgkp2 at gmail dot com)
-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Cannot reproduce – Re: [r12-4632 Regression] FAIL: gfortran.dg/bind-c-intent-out-2.f90 -Os (test for excess errors) on Linux/x86_64
  2021-10-23  6:19 ` Cannot reproduce – " Tobias Burnus
@ 2021-10-23 12:31   ` H.J. Lu
  2021-10-23 12:34     ` H.J. Lu
  0 siblings, 1 reply; 5+ messages in thread
From: H.J. Lu @ 2021-10-23 12:31 UTC (permalink / raw)
  To: Tobias Burnus; +Cc: Sunil K Pandey, GCC Patches, gcc-regression

On Fri, Oct 22, 2021 at 11:20 PM Tobias Burnus <tobias@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?

> Tobias
>
> On 23.10.21 06:43, sunil.k.pandey wrote:
> > On Linux/x86_64,
> >
> > 24e99e6ec1cc57f3660c00ff677c7feb16aa94d2 is the first bad commit
> > commit 24e99e6ec1cc57f3660c00ff677c7feb16aa94d2
> > Author: Tobias Burnus <tobias@codesourcery.com>
> > Date:   Fri Oct 22 23:23:06 2021 +0200
> >
> >      Fortran: Avoid running into assert with -fcheck= + UBSAN
> >
> > caused
> >
> > FAIL: gfortran.dg/bind-c-intent-out-2.f90   -O0  (test for excess errors)
> > FAIL: gfortran.dg/bind-c-intent-out-2.f90   -O1  (test for excess errors)
> > FAIL: gfortran.dg/bind-c-intent-out-2.f90   -O2  (test for excess errors)
> > FAIL: gfortran.dg/bind-c-intent-out-2.f90   -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions  (test for excess errors)
> > FAIL: gfortran.dg/bind-c-intent-out-2.f90   -O3 -g  (test for excess errors)
> > FAIL: gfortran.dg/bind-c-intent-out-2.f90   -Os  (test for excess errors)
> >
> > with GCC configured with
> >
> > ../../gcc/configure --prefix=/local/skpandey/gccwork/toolwork/gcc-bisect-master/master/r12-4632/usr --enable-clocale=gnu --with-system-zlib --with-demangler-in-ld --with-fpmath=sse --enable-languages=c,c++,fortran --enable-cet --without-isl --enable-libmpx x86_64-linux --disable-bootstrap
> >
> > To reproduce:
> >
> > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gfortran.dg/bind-c-intent-out-2.f90 --target_board='unix{-m32}'"
> > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gfortran.dg/bind-c-intent-out-2.f90 --target_board='unix{-m32\ -march=cascadelake}'"
> > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gfortran.dg/bind-c-intent-out-2.f90 --target_board='unix{-m64}'"
> > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gfortran.dg/bind-c-intent-out-2.f90 --target_board='unix{-m64\ -march=cascadelake}'"
> >
> > (Please do not reply to this email, for question about this report, contact me at skpgkp2 at gmail dot com)
> -----------------
> Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955



--
H.J.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Cannot reproduce – Re: [r12-4632 Regression] FAIL: gfortran.dg/bind-c-intent-out-2.f90 -Os (test for excess errors) on Linux/x86_64
  2021-10-23 12:31   ` H.J. Lu
@ 2021-10-23 12:34     ` H.J. Lu
  2021-10-23 12:43       ` H.J. Lu
  0 siblings, 1 reply; 5+ messages in thread
From: H.J. Lu @ 2021-10-23 12:34 UTC (permalink / raw)
  To: Tobias Burnus; +Cc: Sunil K Pandey, GCC Patches

On Sat, Oct 23, 2021 at 5:31 AM H.J. Lu <hjl.tools@gmail.com> wrote:
>
> On Fri, Oct 22, 2021 at 11:20 PM Tobias Burnus <tobias@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.

> > Tobias
> >
> > On 23.10.21 06:43, sunil.k.pandey wrote:
> > > On Linux/x86_64,
> > >
> > > 24e99e6ec1cc57f3660c00ff677c7feb16aa94d2 is the first bad commit
> > > commit 24e99e6ec1cc57f3660c00ff677c7feb16aa94d2
> > > Author: Tobias Burnus <tobias@codesourcery.com>
> > > Date:   Fri Oct 22 23:23:06 2021 +0200
> > >
> > >      Fortran: Avoid running into assert with -fcheck= + UBSAN
> > >
> > > caused
> > >
> > > FAIL: gfortran.dg/bind-c-intent-out-2.f90   -O0  (test for excess errors)
> > > FAIL: gfortran.dg/bind-c-intent-out-2.f90   -O1  (test for excess errors)
> > > FAIL: gfortran.dg/bind-c-intent-out-2.f90   -O2  (test for excess errors)
> > > FAIL: gfortran.dg/bind-c-intent-out-2.f90   -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions  (test for excess errors)
> > > FAIL: gfortran.dg/bind-c-intent-out-2.f90   -O3 -g  (test for excess errors)
> > > FAIL: gfortran.dg/bind-c-intent-out-2.f90   -Os  (test for excess errors)
> > >
> > > with GCC configured with
> > >
> > > ../../gcc/configure --prefix=/local/skpandey/gccwork/toolwork/gcc-bisect-master/master/r12-4632/usr --enable-clocale=gnu --with-system-zlib --with-demangler-in-ld --with-fpmath=sse --enable-languages=c,c++,fortran --enable-cet --without-isl --enable-libmpx x86_64-linux --disable-bootstrap
> > >
> > > To reproduce:
> > >
> > > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gfortran.dg/bind-c-intent-out-2.f90 --target_board='unix{-m32}'"
> > > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gfortran.dg/bind-c-intent-out-2.f90 --target_board='unix{-m32\ -march=cascadelake}'"
> > > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gfortran.dg/bind-c-intent-out-2.f90 --target_board='unix{-m64}'"
> > > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gfortran.dg/bind-c-intent-out-2.f90 --target_board='unix{-m64\ -march=cascadelake}'"
> > >
> > > (Please do not reply to this email, for question about this report, contact me at skpgkp2 at gmail dot com)
> > -----------------
> > Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955
>
>
>
> --
> H.J.



-- 
H.J.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Cannot reproduce – Re: [r12-4632 Regression] FAIL: gfortran.dg/bind-c-intent-out-2.f90 -Os (test for excess errors) on Linux/x86_64
  2021-10-23 12:34     ` H.J. Lu
@ 2021-10-23 12:43       ` H.J. Lu
  0 siblings, 0 replies; 5+ messages in thread
From: H.J. Lu @ 2021-10-23 12:43 UTC (permalink / raw)
  To: Tobias Burnus; +Cc: Sunil K Pandey, GCC Patches

On Sat, Oct 23, 2021 at 5:34 AM H.J. Lu <hjl.tools@gmail.com> wrote:
>
> On Sat, Oct 23, 2021 at 5:31 AM H.J. Lu <hjl.tools@gmail.com> wrote:
> >
> > On Fri, Oct 22, 2021 at 11:20 PM Tobias Burnus <tobias@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.tools@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.

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2021-10-23 12:43 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-10-23  4:43 [r12-4632 Regression] FAIL: gfortran.dg/bind-c-intent-out-2.f90 -Os (test for excess errors) on Linux/x86_64 sunil.k.pandey
2021-10-23  6:19 ` Cannot reproduce – " Tobias Burnus
2021-10-23 12:31   ` H.J. Lu
2021-10-23 12:34     ` H.J. Lu
2021-10-23 12:43       ` H.J. Lu

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).