public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Tobias Burnus <tobias@codesourcery.com>
Cc: Sunil K Pandey <skpgkp2@gmail.com>,
	GCC Patches <gcc-patches@gcc.gnu.org>,
	 gcc-regression@gcc.gnu.org
Subject: 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
Date: Sat, 23 Oct 2021 05:31:02 -0700	[thread overview]
Message-ID: <CAMe9rOo73PqCFY54SuQaVcb9kLuVCURVfA-y84dnHLVUd=Bw+Q@mail.gmail.com> (raw)
In-Reply-To: <9c7d623e-509a-e824-8d85-e3b511cb88d1@codesourcery.com>

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.

  reply	other threads:[~2021-10-23 12:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-23  4:43 sunil.k.pandey
2021-10-23  6:19 ` Cannot reproduce – " Tobias Burnus
2021-10-23 12:31   ` H.J. Lu [this message]
2021-10-23 12:34     ` H.J. Lu
2021-10-23 12:43       ` H.J. Lu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAMe9rOo73PqCFY54SuQaVcb9kLuVCURVfA-y84dnHLVUd=Bw+Q@mail.gmail.com' \
    --to=hjl.tools@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc-regression@gcc.gnu.org \
    --cc=skpgkp2@gmail.com \
    --cc=tobias@codesourcery.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).