From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id B79B43858D28; Mon, 19 Jun 2023 12:45:49 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B79B43858D28 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1687178749; bh=r8SnYqHBjXSOihbYYfOyJU4OxCWwEkFmt5y8xYICg/c=; h=From:To:Subject:Date:From; b=fS5TyrYLtyyuVF0gz+XeRYW6Cv9rp/weY/gSf0C6a+JaStmNvi2jiE3fNbVqSzVs+ Td3PqPtXDizzeRXILOQHSfNLXJ0MXbwoHuPhRXg5vB4ZcxUIWv80ojDdn8v2y+OFqp qzpCOHCgXuGeAu3iQ7ns564jYm1X0JE0sat+QyoM= From: "juergen.reuter at desy dot de" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/110311] New: [gfortran 14.0 regression] Date: Mon, 19 Jun 2023 12:45:49 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: juergen.reuter at desy dot de X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D110311 Bug ID: 110311 Summary: [gfortran 14.0 regression] Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: juergen.reuter at desy dot de Target Milestone: --- Hi, let me open up an issue already. I believe there was a regression introduce= d in gfortran between June 11 and June 19, as our CI with a git-clone built gcc/gfortran worked last week, and fails this week. Two out of our ca. 340 functional tests fail because they return zero results. I will try to boil = this down to a smaller reproducer (fingers crossed), but if you want to play aro= und already, checkout our code from here: https://gitlab.tp.nt.uni-siegen.de/whizard/public Note that you need noweb and OCaml besides gcc/gfortran. Do in the main directory ./build_master.sh and autoreconf, then in a build directory _buil= d=20 do ../configure, make -j4, make -C tests/functional_tests -j4 check. The failing tests are nlo_9.run and nlo_10.run in case you want to run them already now. Cheers, Juergen=