public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/96325] Unclassifiable statement with syntax similar to a type-bound procedure call is accepted
Date: Sun, 02 Aug 2020 22:46:24 +0000 [thread overview]
Message-ID: <bug-96325-4-fjGLHpV8RB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96325-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96325
Rainer Orth <ro at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ro at gcc dot gnu.org
--- Comment #18 from Rainer Orth <ro at gcc dot gnu.org> ---
(In reply to CVS Commits from comment #16)
> gcc/testsuite/
> PR fortran/96325
> * gfortran.dg/pr96325.f90: New test.
The new testcase produces
+UNRESOLVED: gfortran.dg/pr96325.f90 -O0 compilation failed to produce
executable
+UNRESOLVED: gfortran.dg/pr96325.f90 -O1 compilation failed to produce
executable
+UNRESOLVED: gfortran.dg/pr96325.f90 -O2 compilation failed to produce
executable
+UNRESOLVED: gfortran.dg/pr96325.f90 -O3 -fomit-frame-pointer -funroll-loops
-fpeel-loops -ftracer -finline-functions compilation failed to produce
executable
+UNRESOLVED: gfortran.dg/pr96325.f90 -O3 -g compilation failed to produce
executable
+UNRESOLVED: gfortran.dg/pr96325.f90 -Os compilation failed to produce
executable
everywhere. It cannot be
! { dg-do run }
when the compilation is expected to fail.
next prev parent reply other threads:[~2020-08-02 22:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-26 20:05 [Bug fortran/96325] New: Invalid call of a type-bound procedure " chilikin.k at gmail dot com
2020-07-26 20:29 ` [Bug fortran/96325] " kargl at gcc dot gnu.org
2020-07-26 20:43 ` chilikin.k at gmail dot com
2020-07-26 20:47 ` chilikin.k at gmail dot com
2020-07-26 20:57 ` chilikin.k at gmail dot com
2020-07-27 0:11 ` [Bug fortran/96325] Unclassifiable statement with syntax similar to a type-bound procedure call " kargl at gcc dot gnu.org
2020-07-28 15:47 ` kargl at gcc dot gnu.org
2020-07-28 21:48 ` chilikin.k at gmail dot com
2020-07-28 22:53 ` kargl at gcc dot gnu.org
2020-07-29 1:46 ` jvdelisle at charter dot net
2020-07-29 2:25 ` kargl at gcc dot gnu.org
2020-07-29 2:46 ` jvdelisle at charter dot net
2020-07-29 14:54 ` pault at gcc dot gnu.org
2020-07-29 16:18 ` sgk at troutmask dot apl.washington.edu
2020-07-29 16:53 ` paul.richard.thomas at gmail dot com
2020-07-29 17:59 ` sgk at troutmask dot apl.washington.edu
2020-08-02 9:35 ` cvs-commit at gcc dot gnu.org
2020-08-02 21:56 ` jvdelisle at charter dot net
2020-08-02 22:46 ` ro at gcc dot gnu.org [this message]
2020-08-03 8:26 ` paul.richard.thomas at gmail dot com
2020-08-03 8:29 ` paul.richard.thomas at gmail dot com
2020-08-03 13:11 ` dominiq at lps dot ens.fr
2020-08-04 6:54 ` cvs-commit at gcc dot gnu.org
2021-01-07 14:59 ` cvs-commit at gcc dot gnu.org
2021-01-07 15:00 ` cvs-commit at gcc dot gnu.org
2021-01-07 16:33 ` cvs-commit at gcc dot gnu.org
2021-01-07 16:34 ` cvs-commit at gcc dot gnu.org
2021-01-07 17:25 ` pault 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-96325-4-fjGLHpV8RB@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).