public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/102500] New: [12 regression] Missing include for gfortran.dg/include_15.f90 in r12-3722
Date: Mon, 27 Sep 2021 16:37:31 +0000 [thread overview]
Message-ID: <bug-102500-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102500
Bug ID: 102500
Summary: [12 regression] Missing include for
gfortran.dg/include_15.f90 in r12-3722
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: seurer at gcc dot gnu.org
Target Milestone: ---
g:417ea5c02cef7f000e66d1af22b066c2c1cda047, r12-3722
make -k check-gcc-fortran RUNTESTFLAGS="dg.exp=gfortran.dg/include_15.f90"
FAIL: gfortran.dg/include_15.f90 -O (test for excess errors)
# of expected passes 2
# of unexpected failures 1
spawn -ignore SIGHUP
/home3/seurer/gcc/git/build/gcc-test/gcc/testsuite/gfortran/../../gfortran
-B/home3/seurer/gcc/git/build/gcc-test/gcc/testsuite/gfortran/../../
-B/home3/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/./libgfortran/
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gfortran.dg/include_15.f90
-fdiagnostics-plain-output -fdiagnostics-plain-output -O -pedantic-errors -cpp
-idirafter /fdaf/ -I bar -Wmissing-include-dirs -S -o include_15.s
<built-in>: Warning: /fdaf/: No such file or directory [-Wmissing-include-dirs]
<built-in>: Warning: bar: No such file or directory [-Wmissing-include-dirs]
<built-in>: Warning: finclude: No such file or directory
[-Wmissing-include-dirs]
PASS: gfortran.dg/include_15.f90 -O (test for warnings, line )
PASS: gfortran.dg/include_15.f90 -O (test for warnings, line )
Executing on host:
/home3/seurer/gcc/git/build/gcc-test/gcc/testsuite/gfortran/../../gfortran
-B/home3/seurer/gcc/git/build/gcc-test/gcc/testsuite/gfortran/../../
-B/home3/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/./libgfortran/
exceptions_enabled3561299.cc -fdiagnostics-plain-output
-fdiagnostics-plain-output -S -o exceptions_enabled3561299.s (timeout =
300)
spawn -ignore SIGHUP
/home3/seurer/gcc/git/build/gcc-test/gcc/testsuite/gfortran/../../gfortran
-B/home3/seurer/gcc/git/build/gcc-test/gcc/testsuite/gfortran/../../
-B/home3/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/./libgfortran/
exceptions_enabled3561299.cc -fdiagnostics-plain-output
-fdiagnostics-plain-output -S -o exceptions_enabled3561299.s
FAIL: gfortran.dg/include_15.f90 -O (test for excess errors)
Excess errors:
<built-in>: Warning: finclude: No such file or directory
[-Wmissing-include-dirs]
commit 417ea5c02cef7f000e66d1af22b066c2c1cda047 (HEAD, refs/bisect/bad)
Author: Tobias Burnus <tobias@codesourcery.com>
Date: Tue Sep 21 08:27:00 2021 +0200
Fortran: Fix -Wno-missing-include-dirs handling [PR55534]
next reply other threads:[~2021-09-27 16:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 16:37 seurer at gcc dot gnu.org [this message]
2021-09-28 6:44 ` [Bug fortran/102500] " tschwinge at gcc dot gnu.org
2021-09-28 7:31 ` burnus at gcc dot gnu.org
2021-09-28 7:52 ` cvs-commit at gcc dot gnu.org
2021-09-28 8:34 ` rguenth at gcc dot gnu.org
2021-09-28 12:05 ` tschwinge at gcc dot gnu.org
2021-09-28 15:05 ` seurer at gcc dot gnu.org
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=bug-102500-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).